Commentary

Larry Greenemeier
 

Keeping EA Demons at Bay

When describing the principles behind a successful state enterprise architecture, Patricia Carlson earlier this week said it should be as practical and flexible as possible and include input from not just state IT professionals but those on the federal and local level as well. Speaking on a panel at the National Association of State CIO's annual conference in New Orleans Monday, Carlson, the Wisconsin Department of Administration's chief enterprise architect, used a "nonexample" to make her point (I learned about nonexamples as an undergrad but haven't thought much about them over the past decade).
When describing the principles behind a successful state enterprise architecture, Patricia Carlson earlier this week said it should be as practical and flexible as possible and include input from not just state IT professionals but those on the federal and local level as well. Speaking on a panel at the National Association of State CIO's annual conference in New Orleans Monday, Carlson, the Wisconsin Department of Administration's chief enterprise architect, used a "nonexample" to make her point (I learned about nonexamples as an undergrad but haven't thought much about them over the past decade).An enterprise architecture should not be like the Winchester Mystery House, she said, in reference to the 160-room mansion built by the gun magnate's widow, Sarah Winchester, in the late 1800s. Legend has it, Mrs. Winchester had the mansion built over a period of 38 years and kept adding rooms to assuage (and protect herself from) the spirits of the many victims killed by Winchester rifles. The house is a marvel of building creativity and innovation, yet it's completely uninhabitable, Carlson said.

Applied to public-sector IT, the Winchester House shows what happens when you have a hundred builders but no architects, Carlson noted. To avoid Winchester House-inspired IT projects, states need to develop standards and guidelines and create incentives -such as cost savings - for agencies and administrations that comply.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links