Covalent Solutions Inc.®




Why Architecture Matters

Five Fundamentals for Success

Why IT Initiatives Fail

Where to Begin

About Us

Contact Us


Covalent Solutions Inc.®

Bonding Business to Architecture & Technology


Where do we begin

Regardless of talent--or number of bodies--it would be presumptuous if not outright arrogant to assume that our firm, or any other could walk into your business and immediately deliver an IT Architecture without months of background work1 8. So, if your currently have no documented IT Architecture or an incomplete one2 defined, there will likely be several months of data gathering exercises and tons of analysis to perform before actionable architecture elements are achievable.

Don't despair. You are not alone, hundreds of businesses are facing similar circumstances. Some think the task ahead is too daunting to even begin--so they simply settle for "reference implementations4" in lieu of actual architecture.  While others have a team of architects--on staff--or 'partners' who provide architectural services many are still dissatisfied with the results delivered. In many cases it is because they are not working from the "business out". They are working from the "technology in". Approaching the problem in this fashion, they are unlikely to ever define an architectural blueprint that will stand the test of time--or respond to critical  "ilities5". Architects functioning from a "technology in" perspective will be in a constant struggle to either bend technology or bend business process to respond to the next business challenge/opportunity. And when you do this, your efforts will have few elements of predictability. Erratic performance is more the expected norm.



We would suggest beginning with an assessment engagement. In such an engagement, we meet you where you are. If your are doing actual architectural work, we have tools that can help your team move to new levels of efficiency. If you're not doing architectural work, we can show your team how to begin, and then arrange 'check-point' meetings if your team does not require full-time assistance. While we have suggested service time frames, our services are always fully customizable to meet your needs and budget.

Click to see an example of One of our Approaches

Though we are certified in TOGAF6 as an architectural framework model, we are likewise skilled across the spectrum of industry recognized frameworks, and models. In addition, we've developed proprietary methodologies based on SIx-Sigma practices which we can help you utilize to gain incremental efficiencies. Efficiencies may be realized in everything from Essential Meeting Facilitation Skills, to the conduct of a WorkOut--which is where effective IT Architecture development always begins.

The best way to begin is to simple,  contact us. We will discuss "entry and exit points" for our engagement. Our goal is not to become a permanent fixture in your facility, but a resource to accelerate incremental efficiencies for your organization. As you may have already surmised, we love references to chemistry, so consider us your thought Catalyst7.

The Evolution of Workout

Workout as a business improvement methodology was birthed at GE under Jack Welch in response to failed TQM efforts and Welch's passion to accelerate change and transform GE's bureaucratic culture. The first Workout efforts at GE were built on the construct of the "Town Hall Meeting" - one to three-day gatherings of organization stakeholders designed to discuss and take action on major issues.

The big differences between this first generation of Workout version and TQM and other continuous improvement methodologies were striking, including:

   1. Speed to Action
      Where TQM emphasized study before acting, Workout promoted action as soon as a consensus could be reached on a common-sense solution.


   2. Simplicity of Tools
      Workout favored the use of understandable tools, ready for use by anyone with knowledge of the problem, versus statistical and analytical tools requiring expert training.


   3. Self-confidence to Act
      Workout meetings encouraged open airing of opinions but also demanded personal commitment to action. This emphasis on individual versus team accountability heightened the personal threat, but clearly enhanced follow-through from Workout meetings. 
(Source: http://www.isixsigma.com/library/content/c021104a.asp)




Footnotes:


  1. Anyone who has sincerely developed architectural standards will tell you that requirements gathering alone is not a single, rather a series of meetings. And that is the absolute beginning of the development of an IT Architecture. 
  2. An incomplete architecture may very well be one that is documented but does not deliver predictable outcomes.
  3. Well defined (Principles Based--Business Driven) IT Architectures should be very predictable and have very measurable results.
  4. Reference Implementations often masquerade as Reference Architectures. In reality they are not architecture at all! They are merely 'patterns' for implementing a 'element' that may or may not adhere to an architecture aligned to your business.
  5. "Ilities" is an acronym often used in substitute for characteristics such as: Predictability, Scalability, Accessibility, Serviceability, Securability, etc...
  6. TOGAF, Zachman, DODAF, ITIL are all architectural frameworks which have applicability to a specific set (or range) of architectural requirements.
  7. Catalyst = Chemical agent that accelerates a reaction without being permanently changed in the process, so it can be used over and over.
  8. Have you ever seen the Kohler faucet commercial that begins with a rather pompous design architect walking a couple through his studio, and ends with him asking the couple "what could I, do for you?" The lady then sits an artful faucet on his desk and states, "design a house around this." Though her challenge seems like a formidable one, it also represents an "inside out" approach to architecture. And it also answers a key questions: What are your priorities? IT Architecture is no different. Inside out approaches are best, and best accomplished when key stakeholder priorities are understood.