Jeffrey Blake - Web+Cloud+Strategy

05/11/2011

Cloud Decisions

Belmont-clouds_9

Evolution rather than replacement.

The private cloud can evolve from existing virtualized infrastructure, enabling the transition to cloud computing without a complete and disruptive infrastructure overhaul.

Security and compliance.

With a private cloud, data is retained within the enterprise, behind the corporate firewall, where IT can exercise full control over security, privacy, and regulatory compliance. With public clouds, enterprise data is housed in external data centers—and may move from location to location, without IT’s knowledge or consent. The dynamic movement of data in a public cloud may also present compliance challenges with local regulations.

Service level agreements (SLAs).

Keeping applications in-house can help IT continue to meet SLAs deining performance, availability, and other critical business requirements. Some external providers may not be able to furnish the same level of service.

Cost.

A large enterprise private cloud can provide economies of scale, resulting in total cost of ownership (TCO) that is competitive with or lower than public clouds. Intel IT, for example, found that services can be hosted internally at equal or lower TCO than hosting them externally.

Building expertise.

Architecting a private cloud enables IT organizations to develop a knowledge base that can be applied to public clouds in the future. When creating the private cloud, IT will need to develop detailed application and data inventories, and gain key skills such as managing cloud SLAs. This experience will help build effective relationships with public cloud providers, enabling IT organizations to assess whether they meet enterprise requirements

(excerpt from http://www.readwriteweb.com/cloud/cio-agenda-paper-vmware.pdf)

connect with me
Jeffrey Blake

Posted via email from Jeffrey Blake - The Enterprise Architect | Comment »

Enhanced by Zemanta

7 Primary Business Drivers for Social Media

  • Enhance branding and awareness
  • Protect reputation
  • Extend public relations
  • Build community or loyalty
  • Extend customer service
  • Facilitate research and development
  • Drive sales or leads
connect with me
Jeffrey Blake

Posted via email from Jeffrey Blake - The Enterprise Architect | Comment »

Social Network Users’ Bill of Rights

1.Honesty: We will honor our privacy policy and terms of service.

2. Clarity: We will make sure that our policies, terms of service, and settings are easy to find and understand.

3. Freedom of speech: We will not delete or modify user data without a clear policy and justification.

4. Empowerment : We will support assistive technologies and universal accessibility.

5. Self-protection: We will support privacy-enhancing technologies.

6. Data minimization: We will minimize the information users are required to provide and share with others.

7. Control: We will work toward enabling users to own and control their data and won’t facilitate sharing their data unless they agree first.

8. Predictability: We will obtain the prior consent of users before significantly changing who can see their data.

9. Data portability: We will make it easy for users to obtain a copy of their data.

10. Protection: We will treat user data as securely as our own confidential data unless they choose to share these data, and notify them if these data are compromised.

11. Right to know: We will show users how we are using their data and allow them to see who and what has access to their data.

12. Right to self-define: We will allow users to create more than one identity and use pseudonyms. We will not link them without their permission.

13. Right to appeal: We will allow users to appeal punitive actions.

14. Right to withdraw: We will allow users to delete their accounts and remove their data.

via blog.diasporafoundation.org

connect with me
Jeffrey Blake

Posted via email from Jeffrey Blake - The Enterprise Architect | Comment »

The 5 Laws of Engagement

Law 1: We seek comfort in relationships: Surround us with community, which we’ve seen success with like Facebook, Twitter and 4chan. Most interestingly is PostSecret, an ongoing community art project where people mail in their secrets anonymously on one side of a homemade postcard.

Law 2: We all have something to say. So give us tools to express ourselves. Tools include comments, notes, and all the fun things Facebook has given us with Timeline, etc.

Law 3: We need to feel important. Use rewards to make us feel special. How do you make people feel special? One way is through exclusivity like Gilt Group. One way is through badges on Foursquare.

Law 4: We are hypnotized by beauty. Give us something beautiful to look out. Flipboard puts the image first. Instagram is a series of beautiful images within a community.

Law 5: We are captivated by the unknown. So target our curiosity. Foursquare does this with points! Pinterest does with page after page of constant intrigue.

connect with me
Jeffrey Blake

Posted via email from Jeffrey Blake - The Enterprise Architect | Comment »

09/09/2011

Anne Boe’s Keys to Successful Networking

  1. Clarify your career goals.
  2. Develop long-term win-win relationships.
  3. Nurture your network daily.
  4. Be actively involved in your community.
  5. Meet as many people as you can.
  6. Take your business cards everywhere.
  7. Make friends, even when you don’t need them.
  8. Act like a host, not a guest.
  9. Become an interested person.
  10. Develop your listening skills.
  11. Trust your intuition.
  12. Take people risks.
  13. Master the art of small talk.
  14. Work smarter, not harder.
  15. Value yourself and your life.
  16. Take action daily towards your goals.
  17. Become your own energy manager.
  18. Learn to ask for what you want.
  19. Give thanks for what you have.
  20. Acknowledge your skills and talents.
  21. Say “Thank you. “
  22. Become an inverse paranoid - decide the world is conspiring for you.
  23. Determine your priorities - protect your energy.
  24. Learn to want what you have.
  25. Know that there are more side doors in the world than there are front doors.

[Source: Anne Boe]

    Posted via email from Jeffrey Blake - The Enterprise Architect | Comment »

    08/09/2011

    Creating an IT Strategy - Management by Maxim

    I have heard that 90% of all businesses do not have a written Business Strategy.  Its in their heads - but as an Enterprise Architect how do you extract it so that you can create a viable IT Strategy?  Often times CxOs don’t have time to have a strategic dialogue.  One way to solve this problem is to employ the “Maxim Process”

    The Maxim Process is described by Broadbent and Kitzis in [Broadbent+05] as a pragmatic way to extract enough information for a good enough IT strategy while not investing more than a day’s workshop with senior management. The CIO will organize a work-­‐ shop with CxOs, which will lead to documenting 2 kinds of so-­‐called Maxims:

    • Business Maxims
    • And as a result IT Maxims

    Maxims are a few concise principles that are used to document the strategic direction of an enterprise. A Maxim workshop will usually not produce more than around 5 business maxims. For each of those, management will derive 4-­‐5 maxims for the IT function that will help to support them.

    Maxim

    A typical Maxim Workshop will be split up into two parts:

    • Part 1: Finding the Business Maxims,
    • Part 2: Deriving the IT Maxims

    An external facilitator should moderate the workshop day and process.

    To give examples imagine an old economy financial service provider like a big insurance company that runs more than one brand name on the market. For such an enterprise you could find the following business maxim:

    • Create synergies in back office and service functions wherever brand identity is not compromised

    IT maxims that could be deducted from such a business strategy could be:

    • Define standard architectures and platforms used by all of the group’s companies in order to leverage synergies and to reduce IT cost
    • Harmonize the IT application systems for the group’s companies wherever there is a business case for this.

    SOURCE: TOGAF9 QuickStart Guide 2009

    connect with me
    Jeffrey Blake

    Posted via email from Jeffrey Blake - The Enterprise Architect | Comment »

    26/08/2011

    What Does an Enterprise Architect Do ?

    Business Technology Strategy

    What You Know

    What You Do

    What You Are

    • Your organization’s business and technology strategy and rationale
    • Your competition (products, strategies and Processes)
    • Your company’s business practices
    • Your Technology Portfolio
    • Influence business strategy
    • Translate business strategy into technical vision and strategy
    • Understand customer and market trends
    • Capture customer, organizational and business requirements of architecture
    • Prepare architectural documents and presentations
    • Visionary
    • Entrepreneurial

    Organizational Politics

    What You Know

    What You Do

    What You Are

    • Who the key players are in the organization
    • What they want, both business and personal
    • Communicate, Communicate, Communicate
    • Listen, network and influence
    • Sell the Vision, keep the vision alive
    • Take and retake the pulse of all critical influencers of the architecture project
    • Able to see from and sell to multiple viewpoints
    • Confident and articulate
    • Ambitious and driven
    • Patient and not
    • Resilient
    • Sensitive to where the power is and how it flows in your organization

    Consulting

    What You Know

    What You Do

    What You Are

    • Elicitation techniques
    • Consulting frameworks
    • Soft Skill techniques
    • Build “trusted advisor” relationships
    • Understand what the business people want and need from the architecture
    • Understand what the developers want and need from the  architecture
    • Help developers see the value of the enterprise architecture and understand how to use the technology successfully
    • Committed to others’ success
    • Empathetic and approachable
    • An effective change agent and process savvy
    • A good mentor and teacher

    Leadership

    What You Know

    What You Do

    What You Are

    • Yourself
    • Set team context and vision
    • Make decisions stickp>
    • Build teams
    • Motivate
    • You and others see you as a leader
    • Charismatic and credible
    • You believe it can an should be done and that you can lead the effort
    • Committed, dedicated, passionate
    • You see the entire effort in a broader business and personal context

    Technology

    What You Know

    What You Do

    What You Are

    • In-depth understanding of the domain and pertinent technologies
    • Understand what technical issues are key to success
    • Development of methods and modeling techniques
    • Modeling
    • Trade-off Analysis
    • Prototype, Experiment, and Simulate
    • Prepare architectural documents and presentations
    • Technology trend analysis/roadmaps<
    • Take a systems viewpoint
    • Creative
    • Investigative, Practical, Pragmatic, and Insightful
    • Tolerant of ambiguity, willing to backtrack, seek multiple solutions
    • Good a working at an abstract level

    Risks and Rewards

    Risks

    Rewards

    • Responsibility without corresponding control
    • A lot of resistance and disappointments along the way
    • Often encounter others that believe they have a better idea or solution
    • Focus on interesting and complex issues
    • Opportunity to advance to very high levels in the organization with business and technical focus (rather than personal and fiscal)
    • Opportunity to make an enormous difference to the company and clients


    Source: IFEAD

    connect with me
    Jeffrey Blake

    Posted via email from Jeffrey Blake - The Enterprise Architect | Comment »

    21/07/2011

    Kim Cameron’s 7 Laws of Identity

    Identity


    1. User Control and Consent:

    Digital identity systems must only reveal information identifying a user with the user’s consent. 

    2. Limited Disclosure for Limited Use

    The solution which discloses the least identifying information and best limits its use is the most stable, long-term solutio.

    The Law of Fewest Parties

    Digital identity systems must limit disclosure of identifying information to parties having a necessary and justifiable place in a given identity relationship.

    4. Directed Identity

    A universal identity metasystem must support both “omnidirectional” identifiers for use by public entities and “unidirectional” identifiers for private entities, thus facilitating discovery while preventing unnecessary release of correlation handles.  

    5. Pluralism of Operators and Technologies:

    A universal identity metasystem must channel and enable the interworking of multiple identity technologies run by multiple identity providers.  

    6. Human Integration:

    A unifying identity metasystem must define the human user as a component integrated through protected and unambiguous human-machine communications.  

    7. Consistent Experience Across Contexts:

    A unifying identity metasystem must provide a simple consistent experience while enabling separation of contexts through multiple operators and technologies.

    connect with me
    Jeffrey Blake

    Posted via email from Jeffrey Blake - The Brand Hammer | Comment »

    16/07/2011

    Ten Topics a Venture Capitalist Cares About

    Venture-capital-failure-rates
    According to Guy Kawasaki The ten topics that a venture capitalist cares about are:1. Problem
    2. Your solution
    3. Business model
    4. Underlying magic/technology
    5. Marketing and sales
    6. Competition
    7. Team
    8. Projections and milestones
    9. Status and timeline
    10. Summary and call to action

    [Image courtesy of FreeDigitalPhotos.net]
    connect with me
    Jeffrey Blake

    Posted via email from Jeffrey Blake - The Brand Hammer | Comment »

    01/06/2011

    Five Ways to Organize Information

    In his book Information Anxiety, Richard Saul Wurman notes that there are five basic ways to organize information:

    • Alphabet: The organizing principle used by dictionaries and telephone books.
    • Category: The segmentation of things by attribute or functionality, such as color (shirts) or capabilities (product line).
    • Continuum: Similar to category, but rather than using discrete buckets, this uses a range of values that are expressed in numbers or units. Examples of these magnitude measures include from small to large or from light to heavy. A list of products ordered by price would be a continuum; at the same time, the products could be categorized as inexpensive, moderate, or expensive.
    • Location: Physical location — in geography, points on a map; in anatomy, muscle groups; in an equipment manual, an exploded drawing.
    • Time: A timeline or a set of eras, useful when describing product or organizational history.

     

    Posted via email from Jeffrey Blake - The Brand Hammer | Comment »

    page 1 of 9 | next »
    Tumblr » powered Sid05 » templated