Business architecture always adapt to your audience - 4 tips

on Thursday, 22 August 2013. Posted in Business Analysis, Solution & Business Architecture, Blog

Business architecture always adapt to your audience - 4 tips

 

Always make a point to understand your audience, audience analysis involves identifying the audience and adapting a speech to their interests, level of understanding, attitudes, and beliefs. Taking an audience-centered approach is important because your material effectiveness will be improved if the deliverable is created and delivered in an appropriate manner.

I have seen many times technical people speaking to the business and not talking at the right level and emphasizing technical information like security, protocols and interfaces. An example application A will push the actuals to application B (good) instead of saying Application A attributes are connecting to table AR_Actuals and the trigger releases the information into Application B table GL_Open_balances. 

Depending on your audience adapt your architecture diagrams accordingly.

In my view, here is a sample architecture of a business architecture diagram that will connect with business savvy people to initiate architecture discussions. here are my tips:

  1. A Business Architecture must be process centric
  2. Be able to apply enterprise-wide architecture and process-level models and techniques that are aligned to your roadmap
  3. Develop a measurable architecture for planning, budgeting, organization design, compliance, human change management, and the introduction of breakthrough technologies
  4. Be able to use an architecture model to accelerate capability change projects and model development

 architecture

 Do you have any favorite tips or would like to share your experience on this topic?

Comments (7)

  • Dominique Rivard

    Dominique Rivard

    22 August 2013 at 19:26 |
    Great post, so true we tend sometimes not too understand each other between business and IT, visual diagrams always help
  • Sharanya Patel

    Sharanya Patel

    22 August 2013 at 19:29 |
    Nice post! Another good idea: organize a common vocabulary and enter a contest to win prizes. If the common vocabulary is respected.
  • Carol Dawson

    Carol Dawson

    22 August 2013 at 20:02 |
    Thanks! That's a good scenario. what works well with me is using process models and be decisive when working with developers to avoid feature creep!
  • William Morris

    William Morris

    22 August 2013 at 20:25 |
    I would add set realistic deadlines with IT, and stick to them and don't call a meeting if no decision is planned to be taken. Nice blog will retweet.
  • Justin Drew

    Justin Drew

    22 August 2013 at 21:03 |
    No matter how smart someone is or how impressive the big words sound, if that person cannot communicate without using techno babble he will cost you more money in the long run. Possibly lots of extra money. The really smart people who can help you best are the ones who can also communicate in a business and IT language. Nice post!
  • Lynda Myers

    Lynda Myers

    22 August 2013 at 21:45 |
    I believe communication differences is one of the major reasons for project delays, good point in using visual diagrams that speak well to both parties.
  • Mario Stewart

    Mario Stewart

    23 August 2013 at 04:05 |
    Great post, at our company it has always been an issue we make sure to always use visual diagrams.

Copyright 2014 Appsconsultant.com. All rights reserved.