Albus Consulting Limited | New Concept: Solution Design
50815
post-template-default,single,single-post,postid-50815,single-format-standard,qode-core-1.0.3,ajax_fade,page_not_loaded,,brick-ver-1.4, vertical_menu_with_scroll,smooth_scroll,wpb-js-composer js-comp-ver-4.5.3,vc_responsive

New Concept: Solution Design

Where does solution design fit within the enterprise view of the world? Well, it’s not traditional.  To understand a Solution Designer we need to paint the traditional picture first. Traditional goes something like this:

 

  1. You (business owner) declare a need, follow the prescribed process and get the attention of the IT investigation arm.
  2. An Engagement Manager or Service Delivery Manager (SDM) comes and buys you a coffee and takes some cursory notes. You may see them at the end of the process or if you make noise during the process.
  3. A Business Analyst (BA) responds to the call and initiates contact with you. The BA gets sent to end users and some Subject Matter Experts (SME) and compiles either a list of requirements, or if your environment is more ‘mature’, compiles a Unified Modelling Language (UML) description or the requirement.
  4. The BA then hands the requirements to the Solution Architect, who then again approaches the customer (You) to clarify any uncertainties before she goes away and produces first a Solution Options and Delivery Approach (SODA) document and then next a Solution Architecture Document (SAD).
  5. Before the Solution Architect can however proceed with anything productive she needs to hand the SAD over to the ARB (sorry, Architecture Review Board) that is run by a dedicated bunch of EAs (sorry, that’s Enterprise Architects) who will not let anything pass that, well, doesn’t pass muster.
  6. Once the ARB has approved the SAD, the Solution Architect then hands the SAD to a development team who will again approach the customer (You, again, and again it seems) to clarify any uncertainties before he builds the solution. The developer also needs to do unit testing, systems testing and write a least an As Built Document (ABD, won’t reference this again).
  7. The developer then hands the solution over to the tester who may well need to approach the customer (you guessed it), again, to make sure that the results of this elaborate game of Chinese whispers has not produced something that you had not wanted it the first place.
  8. This is a very serious business.
  9. You pay lots of money for good process.
  10. Sometimes this is the right thing to do.

 

When we however assign you a Solution Designer he will become first and foremost a trusted advisor to you.

 

He will spend some time to understand your needs before ensuring you get a very good SODA which will guide you straight to the key investment options you have.  More than that, he will guide you through the most effective use of your money, taking into account your long and short term plans.

 

He will also take ownership of producing the key design documents required to enact your vision, he will put things through your organisation’s processes on your behalf, and will lead whatever technical resources are required to produce your solution.

 

And lastly, the Solution Designer will oversee the quality assurance activities to match what he had heard for you at the start, and all the way through.

 

Seriously, through our Solution Designers, we give you what you want.  Pragmatic advice, decisive action, fair representation during internal process, and a good result.

No Comments

Post a Comment