The Venn of IT Solution Success

December 27, 2011

Changing technology in an enterprise requires that you have the following “must have” skills in your people:

  1. Leadership & organization
  2. Business acumen
  3. Technical chops

Normally, labor in a project is divided up according to these specialties – i.e. developers have the technical chops, business analysts have the business chops, project managers organize themselves and everyone else. Throw them all into a pot, stir vigorously and…presto! A successful project.

Hardly. Read more



Open Group 2012: San Francisco

November 27, 2011

We are excited to be presenting at the upcoming Open Group Conference next January in San Francisco. According to the Open Group, the conference “…will focus on the role played by IT and EA within Enterprise Transformation.”

Read more



Welcome to Our Investigative Architecture Training!

October 27, 2011

We are very busy right now, refining our Investigative Architecture Workshop scheduled for next month.

Investigative Architecture is the term we coined back in 2008 for our approach that facilitates the rapid assessment and documentation of ‘as-is’ and proposed IT architectures. Read more



When “Good Enough” isn’t Good Enough

October 11, 2011

So what is this picture? The unhelpful answer is that it is a photo of a sign with a burlap sack on it. I’d like to say that my community thought it would be a cute Halloween decoration, but I cannot. The truth: it is great example of the “good enough” anti-pattern. Read more



How to Flub Your Design Review

September 30, 2011

We would like to share some common approaches that consistently lead to failed design review meetings. They are somewhat embellished for effect, but, sadly, are not all that far removed from real world experiences. If you are interested in an ineffective design review, please be sure to: Read more



Measure Thrice, Cut Once

September 12, 2011

Make sure that your designs are accurate. Read more



Issue Resolution: Understanding the Problem

August 22, 2011

For a Solution Architect, creating the blueprint for a quality product is often only half the job: After all, the greatest design in the world isn’t worth much unless it is accurately implemented. Read more



Facts: The Architect’s “Big Stick”

August 16, 2011

“Speak softly and carry a big stick: You will go far.”
– African Proverb

Diplomat is a key role that Systems Flow’s architects often fill for our clients. Software projects and change initiatives inevitably bring disputes and disagreements over requirements, scope, priority, standards, architectures and solutions. While most project management disciplines offer approaches to managing issues, we have found a basic mantra that keeps us on track: Read more



Buy vs. Build Your Software

August 8, 2011

Most organizations shift back and forth between building and buying software solutions in time with executive leadership shifts. To avoid the resulting IT portfolio churn, each organization should establish the IT strategy that best supports its business model – including decision criteria for build vs. buy – or be condemned to holy wars on every solution design. Our default recommendation is “buy,” and here is why. Read more



Investigative Architecture: The Data Perspective

July 31, 2011

“Investigative Architecture” is a term we at Systems Flow coined a few years ago for a core, overarching discipline of ours. It describes – and prescribes – the sometimes tedious, but always challenging, process that a working architect employs to locate and absorb information about a problem space in order to create usable, professional visual work products that best communicate a solution. Read more



Next Page »