Enterprise Architecture Change is Coming. Are You Ready?

There is an impending change coming. In many ways this change is being driven by the move into The Cloud, (the commoditization of IT) and the move to Bring Your […]

Discipline Is Not a Curse

For those of us in the Enterprise Architecture, impressing the value of discipline on the world that is incentivized to ignore it, is par for the course.  Whether it’s due to great expectations, unrealistic timelines, lack of coherent planning, or all of the above, ensuring and enabling others to follow a method or process with trust that success will not come from taking shortcuts is a Herculean task.

So when we transitioned to a Capability-Driven Startup Incubator model, we essentially doubled down on the belief that if done in a disciplined way, we can help entrepreneurs launch companies that are successful, profitable, and not hampered by capability debt (debt of suboptimal decisions made for expediency or based on incomplete information, or by wrong people in wrong positions.)  You’ll see the results of that bet start appearing in the public light next quarter so you can judge whether our bet is paying off.

It is from a discipline perspective that I ran into a very curious piece on Chicago digital startup community that appeared in PandoDaily.  It centers around defining the “Midwest Mentality” of pragmatism, as follows:

Pragmatism is defined as dealing with issues on a practical level, rather than a theoretical one. What does this mean in the context of startups? Well, it means that there is no “let’s build a cool tool and then figure out the business model”. No. In fact, if you do that here, you don’t belong. That’s a plain fact that I have found very few people disagree with.

And while the author (Trevor Gilbert) goes on to provide both pros and cons of pragmatism, he spends the majority of the article blasting pragmatism in context of digital startups.  He delves into working hours, missing the point that amount of work doesn’t usually correlate to success.  Those of us with kids don’t just stop working once we go home – I see many of my married with kids counterparts firing up the laptop after their kids are in bed.  But we can debate whether parents working 9pm to midnight is more productive than their single counterparts spending that time having fun at a bar – either is simply anecdotal and should be taken with several grains of salt.  It’d just be nice if Trevor thought to research his arguments a bit more.

And in that failure of discipline, he makes and then fails to expound on the major point of why Chicago startup community is so different from Boston or Silicon Valley:

Without hot startups, you are left with the problem of attracting investment and talent with names observers don’t truly know.

Here Trevor inverts the causality in support of his argument.  That is shoddy at best, sensationalist at heart, and substandard thinking at worst.  The cause of few “hot startups” is not our pragmatism.  It’s the fact that there is a “problem of attracting investment and talent with names observers don’t truly know.”

If Trevor actually listened to the Chicago VC community, their investment dollars usually go to people they have built a relationship with – over several years.  It’s not that talent, intelligence, adaptability, and stick-to-it-itiveness of the idea don’t play a role.  It’s that in order to be rated on these measures, the prospective entrepreneur has to clear a very high barrier to entry of building a relationship with the prospective funders.  Perhaps it’s a throwback to the old Chicago politics paradigm of “we don’t want nobody nobody sent.”  But perhaps it’s not strictly a Chicago issue (here’s a WSJ article bemoaning that fact nationwide), just more pronounced here.  Regardless of cause, this state of affairs limits our city to be the backwater of seed investment dollars.  Either way, I’m not sure that “Midwestern Mentality” has much to do with it.

AAB

Discipline Is Not a Curse

For those of us in the Enterprise Architecture, impressing the value of discipline on the world that is incentivized to ignore it, is par for the course.  Whether it’s due to great expectations, unrealistic timelines, lack of coherent planning, or all of the above, ensuring and enabling others to follow a method or process with trust that success will not come from taking shortcuts is a Herculean task.

So when we transitioned to a Capability-Driven Startup Incubator model, we essentially doubled down on the belief that if done in a disciplined way, we can help entrepreneurs launch companies that are successful, profitable, and not hampered by capability debt (debt of suboptimal decisions made for expediency or based on incomplete information, or by wrong people in wrong positions.)  You’ll see the results of that bet start appearing in the public light next quarter so you can judge whether our bet is paying off.

It is from a discipline perspective that I ran into a very curious piece on Chicago digital startup community that appeared in PandoDaily.  It centers around defining the “Midwest Mentality” of pragmatism, as follows:

Pragmatism is defined as dealing with issues on a practical level, rather than a theoretical one. What does this mean in the context of startups? Well, it means that there is no “let’s build a cool tool and then figure out the business model”. No. In fact, if you do that here, you don’t belong. That’s a plain fact that I have found very few people disagree with.

And while the author (Trevor Gilbert) goes on to provide both pros and cons of pragmatism, he spends the majority of the article blasting pragmatism in context of digital startups.  He delves into working hours, missing the point that amount of work doesn’t usually correlate to success.  Those of us with kids don’t just stop working once we go home – I see many of my married with kids counterparts firing up the laptop after their kids are in bed.  But we can debate whether parents working 9pm to midnight is more productive than their single counterparts spending that time having fun at a bar – either is simply anecdotal and should be taken with several grains of salt.  It’d just be nice if Trevor thought to research his arguments a bit more.

And in that failure of discipline, he makes and then fails to expound on the major point of why Chicago startup community is so different from Boston or Silicon Valley:

Without hot startups, you are left with the problem of attracting investment and talent with names observers don’t truly know.

Here Trevor inverts the causality in support of his argument.  That is shoddy at best, sensationalist at heart, and substandard thinking at worst.  The cause of few “hot startups” is not our pragmatism.  It’s the fact that there is a “problem of attracting investment and talent with names observers don’t truly know.”

If Trevor actually listened to the Chicago VC community, their investment dollars usually go to people they have built a relationship with – over several years.  It’s not that talent, intelligence, adaptability, and stick-to-it-itiveness of the idea don’t play a role.  It’s that in order to be rated on these measures, the prospective entrepreneur has to clear a very high barrier to entry of building a relationship with the prospective funders.  Perhaps it’s a throwback to the old Chicago politics paradigm of “we don’t want nobody nobody sent.”  But perhaps it’s not strictly a Chicago issue (here’s a WSJ article bemoaning that fact nationwide), just more pronounced here.  Regardless of cause, this state of affairs limits our city to be the backwater of seed investment dollars.  Either way, I’m not sure that “Midwestern Mentality” has much to do with it.

AAB

The Fun-damental Laws of Enterprise Architecture

This is largely an extract of Wikipedia’s Eponymous Lays page. I have added a few other items along the way. There are 3 sections: Fun Laws, General Laws & Technology…

The Purpose Of A System Is What It Does

This is some dot points from an excellent article by Richard Veryard discussing Stafford Beer’s maxim that the “Purpose Of a System Is What It Does” or “POSIWID“. Richard points…

What is Enterprise Architecture? – A presentation review of Erik Dörnenburg

This is some notes that I took whilst watching a presentation by Erik Dörnenburg (@erikdoe), Head of Technology Europe at ThoughtWorks. The presentation is titled “What is enterprise architecture?” and…

20 Key Concepts Every Enterprise Architects Should Know

This article written by Alex Matthews (@remembermytweet) OK, so here is a quick brainstorm of key concepts that every EA should know. It is literally a 5 minute brainstorm exercise…

Could Anyone Else Use an Extra $600,000?

I am supplementing my Q&A series on the Value of EA & BPA with a wonderful article published on January 30th about one our customers, Chubb Insurance, written by Madeline Weiss, Society for Information Management’s Advanced Practices Council. There is nothing like a great story to  illustrate some of the ways enterprise architecture initiatives are […]

Related posts:

  1. Q&A Series: The Value of EA and BPA In November and December, Gartner released the Magic Quadrants for…
  2. Q&A Series: The Evolution of EA Next up in my Q&A series on EA, I am…
  3. How to use BPM and EA tools to thrive during a recession Laura Mooney, VP of Corporate Communications for Metastorm, authored this…

Related posts brought to you by Yet Another Related Posts Plugin.