Issue Resolution: Understanding the Problem
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”
“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
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
“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