Photo
Link: https://jeffreyblake.tumblr.com/post/125564114956 00
Aggregated enterprise architecture wisdom
Link: https://jeffreyblake.tumblr.com/post/125564114956 00
Link: http://jeffreyblake.tumblr.com/post/125564114956 00
On the opposite side of the spectrum, Burton outlined her baker’s dozen of “worst” enterprise architecture practices. The EA methods that Burton said muddied efforts and missed overall business returns are as follows:
1. No link to business strategic…
On the opposite side of the spectrum, Burton outlined her baker’s dozen of “worst” enterprise architecture practices. The EA methods that Burton said muddied efforts and missed overall business returns are as follows:
1. No link to business strategic planning and budget process.
2. Confusing “IT Architecture” with “Enterprise Architecture.”
3. Lack of governance.
4. Too much standardization.
5. Focusing on the art/language of EA rather than the outcomes.
6. Strictly adhering to architectural frameworks.
7. An “Ivory Tower” approach by IT and EA team members.
8. Lack of communication and feedback.
9. Limiting the teams to IT resources.
10. Missing performance measures.
11. Picking a tool before understanding business needs.
12. Focusing on the current state first and primarily.
13. Thinking that implementation equals completion.
Are you below your target Klout score? Schaefer reveals seven simple ways to climb up the ranks:
- 1. Build a network. The key to increasing a Klout score is similar to finding success on the social web in general: Build a targeted, engaged network of people who would be legitimately interested in you and your content.
- 2. Create meaningful content. Adopt a strategy to create or aggregate meaningful content that your network loves to share with others. Provide links!
- 3. Engage. Actively engage with others in a helpful and authentic way. Ask questions, answer questions and create a dialogue with your followers.
- 4. Don’t scheme. Any gaming behaviors that fall outside the basic strategies will eventually catch up to you. For example, specifically targeting conversations with high Klout influencers will probably be more annoying than successful. If you keep focused on your network strategy and your content strategy, you’ll succeed.
- 5. Interact with everyone. Don’t be afraid to interact with Klout users with lower scores – it won’t hurt your own score. In fact, it helps build their score and in turn makes you more of an influencer.
- 6. Publish. Remember, you don’t have to make a movie or be elected to office to have power now. All you need to do is publish. Access to free publishing tools such as blogs, video and Twitter have provided users with an opportunity to have a real voice, so take advantage of these many platforms.
- 7. Keep at it. Don’t be discouraged by your score. It’s more important to just enjoy your social media experience and let the chips fall where they may.
Are you below your target Klout score? Schaefer reveals seven simple ways to climb up the ranks:
1. Build a network. The key to increasing a Klout score is similar to finding success on the social web in general: Build a targeted, engaged network of …
1. Distance doesn’t matter.
Employees now expect to be able to collaborate in real-time with any co-worker. They expect to have access to whatever data or services the company offers no matter where they happen to be. Where in the world that co-worker…
1. Distance doesn’t matter.
Employees now expect to be able to collaborate in real-time with any co-worker. They expect to have access to whatever data or services the company offers no matter where they happen to be. Where in the world that co-worker actually works is irrelevant. They may be working from home, different offices, at airports, manufacturing facilities, or even on a ship somewhere. Knowledge workers need the flexibility to work wherever they must in order to best complete their jobs. That may mean on-site, at a customer’s office, or even from the quiet of their own home. IT must be an enabler for the way business needs to operate. Waiting 20 minutes for a file to be sent between workers – even if they are across the world from each other – is no longer acceptable for the employee or for the customer project that they are working on.
2. Business never stops.
With a globalized workforce – and a rapidly globalizing customer base – businesses cannot afford their operations to be stopped for even a few minutes. Responsiveness to disaster or failure – often characterized by recovery point objective (RPO) and recovery time objective (RTO) – must go far beyond responding to common problems like a failed SAN or a downed fiber connection. Issues like hurricanes or a flu pandemic might force workers to operate from home for an unspecified period of time. Compromised data centers may require enterprise to rapidly switch operations to secondary locations with no loss in information.
3. Applications and data must be available everywhere but all in one place.
With organizations working harder to protect their valuable data and sensitive customer information, many IT organizations are engaging in IT consolidation projects. Consolidating data makes it easier to track, protect, and restore. Beginning with remote tape backup and progressing to more complicated projects like file servers, document management applications, PLM systems, and Web applications, CIOs are demanding that data be brought back from remote offices. At the same time, businesses recognize that the data and applications were “out there” for a reason – that’s where they needed to be accessed. So while consolidation is an important strategy for data protection and cost control, it can negatively impact business operations unless LAN-like performance can be maintained everywhere.
4. Knowledge must be harnessed – and data must be managed.
Consolidation goes a long way to eliminating the islands of storage and data that evolve over time. But with organizations being required to react quickly in the face of
change, or move in order to take advantage of an opportunity, flexibility in moving data and applications is essential. CIOs must be able to quickly move massive amounts of data, and potentially set up application infrastructure in remote locations overnight. New offices and merged/acquired businesses must quickly be absorbed into the fabric of the existing organization by providing them immediate access to new systems and data.5. There are no second-class enterprise citizens.
The days of the “important” people working at corporate HQ are rapidly fading. Employees everywhere are now empowered to make important decisions. Whether it is designing or manufacturing a product, working with a customer, or working on a localized version of an advertising campaign, work happens everywhere. And the work of the distributed employee isn’t less important than anyone else’s work. Just as importantly, these workers need to interact with their colleagues, applications and data everywhere. CIOs and IT managers may no longer prioritize workers based on their geographic location. Every member of the enterprise needs to have access to the same applications, at the same level of application performance.
from “The CIO’s new guide to design of global IT infrastructure”
The Cynefin framework has five domains. The first four domains are:
Simple, in which the relationship between cause and effect is obvious to all, the approach is to Sense – Categorise – Respond and we can apply best practice.
Complicated, in which th…
The Cynefin framework has five domains. The first four domains are:
Simple, in which the relationship between cause and effect is obvious to all, the approach is to Sense – Categorise – Respond and we can apply best practice.
Complicated, in which th…
Online Ticketing for How to Fund Your Business Idea powered by Eventbrite
Permalink
| Leave a comment »
On the opposite side of the spectrum, Burton outlined her baker’s dozen of “worst” enterprise architecture practices. The EA methods that Burton said muddied efforts and missed overall business returns are as follows:
1. No link to business strategic planning and budget process.
2. Confusing “IT Architecture” with “Enterprise Architecture.”
3. Lack of governance.
4. Too much standardization.
5. Focusing on the art/language of EA rather than the outcomes.
6. Strictly adhering to architectural frameworks.
7. An “Ivory Tower” approach by IT and EA team members.
8. Lack of communication and feedback.
9. Limiting the teams to IT resources.
10. Missing performance measures.
11. Picking a tool before understanding business needs.
12. Focusing on the current state first and primarily.
13. Thinking that implementation equals completion.