Share this
Using clarity to build trust as a business analyst
by John Barris on 15 December 2010
Lately, together with some of my business analyst colleagues, I have developed a strong interest in the disciplines of Business Architecture and Enterprise Analysis. I have seen it as a powerful vehicle for providing context to projects and programs of work, helping management make investment decisions and mapping change onto their various organisational units.
I noticed that thinking is developing rather rapidly in this field, but as with many of these things everyone has a view and to some extent jargon is starting to exert its dominion. It is easy to clutter a discipline with words that mean nothing to anyone other than to those that play in that playground. However, if we do this with business architecture, we ignore at our own peril the very customers that we serve, the business stakeholders.
Recently I was working with a colleague within an organisation to help them understand the context of a large program of work. We decided to apply some of the Business Architecture concepts we have adopted such as Primary Activities and Business Capabilities. We produced a diagram (which by the way didn’t follow any standards but simply communicated these concepts) and used a spreadsheet to define and map these concepts to requirements. Then we tested it, at a large workshop and guess what: it worked! While there were different views as to what the processes should be they had a reference and a “picture” to discuss.
Not long after the workshop one of the business people was asking a business analyst to explain the concepts in the diagram. He referred them to some definitions we had prepared, for example we had defined a Primary Activity as “something the business does”. Straight away the person said “I can understand that!”
So what do you reckon? Is it time we as business analysts speak plainly even though we may risk some vagueness or would you rather be 100% precise and risk losing the customer? Don’t get me wrong requirement specifications need to be specific, testable and yes unambiguous but communication above all things needs to be understandable.
I believe one of the reasons the business do not trust IT is because they don’t understand it. Some folk may relish the need to be needed even if it is to explain something that they obscured in the first place. I’d rather be trusted because I make myself clear.
Share this
- Agile Development (89)
- Software Development (68)
- Scrum (41)
- Agile (32)
- Business Analysis (28)
- Application Lifecycle Management (27)
- Capability Development (23)
- Requirements (21)
- Lean Software Development (20)
- Solution Architecture (19)
- DevOps (17)
- Digital Disruption (17)
- Project Management (17)
- Coaching (16)
- IT Professional (15)
- IT Project (15)
- Knowledge Sharing (13)
- Equinox IT News (12)
- Agile Transformation (11)
- IT Consulting (11)
- Digital Transformation (10)
- Strategic Planning (10)
- IT Governance (9)
- International Leaders (9)
- People (9)
- Change Management (8)
- Cloud (8)
- MIT Sloan CISR (7)
- Working from Home (6)
- Azure DevOps (5)
- Innovation (5)
- Kanban (5)
- Business Architecture (4)
- Continuous Integration (4)
- Enterprise Analysis (4)
- Client Briefing Events (3)
- GitHub (3)
- IT Services (3)
- AI (2)
- Business Rules (2)
- Communities of Practice (2)
- Data Visualisation (2)
- Java Development (2)
- Lean Startup (2)
- Scaling (2)
- Security (2)
- System Performance (2)
- ✨ (2)
- Automation (1)
- FinOps (1)
- Microsoft Azure (1)
- Satir Change Model (1)
- Testing (1)
- March 2025 (1)
- December 2024 (1)
- August 2024 (1)
- February 2024 (3)
- January 2024 (1)
- September 2023 (2)
- July 2023 (3)
- August 2022 (4)
- July 2021 (1)
- March 2021 (1)
- February 2021 (1)
- November 2020 (2)
- July 2020 (1)
- June 2020 (2)
- May 2020 (3)
- March 2020 (3)
- August 2019 (1)
- July 2019 (2)
- June 2019 (1)
- April 2019 (3)
- March 2019 (2)
- December 2018 (1)
- October 2018 (1)
- August 2018 (1)
- July 2018 (1)
- April 2018 (2)
- February 2018 (1)
- January 2018 (1)
- September 2017 (1)
- July 2017 (1)
- February 2017 (1)
- January 2017 (1)
- October 2016 (2)
- September 2016 (1)
- August 2016 (4)
- July 2016 (3)
- June 2016 (3)
- May 2016 (4)
- April 2016 (5)
- March 2016 (1)
- February 2016 (1)
- January 2016 (3)
- December 2015 (5)
- November 2015 (11)
- October 2015 (3)
- September 2015 (2)
- August 2015 (2)
- July 2015 (7)
- June 2015 (7)
- April 2015 (1)
- March 2015 (2)
- February 2015 (2)
- December 2014 (3)
- September 2014 (2)
- July 2014 (1)
- June 2014 (2)
- May 2014 (8)
- April 2014 (1)
- March 2014 (2)
- February 2014 (2)
- November 2013 (1)
- October 2013 (2)
- September 2013 (2)
- August 2013 (2)
- May 2013 (1)
- April 2013 (3)
- March 2013 (2)
- February 2013 (1)
- January 2013 (1)
- November 2012 (1)
- October 2012 (1)
- September 2012 (1)
- July 2012 (2)
- June 2012 (1)
- May 2012 (1)
- November 2011 (2)
- August 2011 (2)
- July 2011 (3)
- June 2011 (4)
- April 2011 (2)
- February 2011 (1)
- January 2011 (2)
- December 2010 (1)
- November 2010 (1)
- October 2010 (1)
- February 2010 (1)
- July 2009 (1)
- October 2008 (1)