Share this
The five Cs for clarity of thought for business analysts
by John Barris on 09 June 2015
As a business analyst, it’s my job to understand a business – any business – and its requirements.
Only then can I communicate what I’ve discovered to stakeholders in a way that allows them to make change decisions, or build a new system to take their business activities to the next level.
And achieving that is all about communication; clear communication and clarity of thought. ‘Achieving clarity of thought’ is a key focus of mine and is also the title of a chapter I contributed to the recently published book, Business Analysis Book of Mentors: 25 Lessons Learned from Seasoned BA Professionals.
In this post, I summarise key takeaways from that chapter, focusing on the five ‘Cs’ that enable clarity of thought from a business analysis perspective.
To help achieve clarity of thought as a business analyst you should focus on:
Context – Where are you working?
A business analyst needs to understand the world in which their client is working to fully grasp the business’ needs. The people, processes, systems and information (together a business capability) of a law enforcement organisation, such as New Zealand Police, is a vastly different context to that of a banking organisation, such as Westpac.
‘Business Architecture’ is a developing discipline that allows business analysts to create a blueprint of the business context. Frameworks, such as Equinox IT’s ‘Enterprise Analysis Framework’ (pictured), help me understand and communicate the context of a particular business and importantly any changes required to that business.
Action: Learn about business architecture and begin applying this in your organisation to gain a clear understanding of your business’ context.
Change – What change are you working on?
It’s vital to know what you need to change and what you don’t. I’ve seen projects lose the context into which they are delivering and start to redefine aspects of the business unnecessarily.
Action: Using your business architecture, get clarity and agreement on the scope of change required to deliver the success criteria (described later in this post). Keep this scope and the business context behind it central to everything you do.
Configuration – What is available and how can you use it?
When the context of a system is defined using clear business language together with business processes, data and rules (that should be managed for the business as a whole), then the process of defining solution requirements becomes more of a configuration exercise.
I prefer to turn around the traditional ‘the system shall’ approach to framing requirements, instead asking what ‘the business requires’ to perform a function or provide a service. The change is then defined in terms of:
- what process needs to be adapted
- what roles need to change
- which functions require automation or system enablement
- what information needs to be used or produced
- what policies need to be created, adjusted, implemented.
Action: Encourage your organisation to start managing business processes, data and rules outside of projects, across the business as a whole. Then begin running your change projects as mechanisms to configure these ‘business assets’ rather than ‘reinventing the wheel’ each time on every new project.
Consensus on success criteria – What’s good enough?
An agreed set of success criteria removes ambiguity, provides a clear target for a project, and maintains its motivation and momentum, thus increasing its ability to succeed.
As a business analyst you play an important role in ensuring that the project delivers what is required by the organisation. Understanding and articulating a clear message of what is required for the project to succeed is fundamental to your role.
Action: Agree and maintain consensus on the success criteria required for your project to succeed.
Collaborating – who are you working with?
We all work better – and enjoy working more – with people we like and whose work we respect. That dynamic can be the ‘make or break’ of any project or initiative. In short, people are just as important as development methodologies.
With that in mind, I apply the principles of ‘people over processes’ and ‘functionality over documentation’.
Action: Create your project and delivery teams using people who collaborate well, are committed to agreed criteria, who understand a business’ context and what needs to change (and what doesn’t), and who contribute to a clear focus on getting the job done.
That’s what we’re all here to do as business analysts. And we can, so long as we speak, think and act with clarity.
For more ideas on clarity as a business analyst, also see my post 3 fundamental questions for achieving clarity as a business analyst.
Share this
- Agile Development (153)
- Software Development (126)
- Agile (76)
- Scrum (66)
- Application Lifecycle Management (50)
- Capability Development (47)
- Business Analysis (46)
- DevOps (43)
- IT Professional (42)
- Equinox IT News (41)
- Agile Transformation (38)
- IT Consulting (38)
- Knowledge Sharing (36)
- Lean Software Development (35)
- Requirements (35)
- Strategic Planning (35)
- Solution Architecture (34)
- Digital Disruption (32)
- IT Project (31)
- International Leaders (31)
- Digital Transformation (26)
- Project Management (26)
- Cloud (25)
- Azure DevOps (23)
- Coaching (23)
- IT Governance (23)
- System Performance (23)
- Change Management (20)
- Innovation (20)
- MIT Sloan CISR (15)
- Client Briefing Events (13)
- Architecture (12)
- Working from Home (12)
- IT Services (10)
- Data Visualisation (9)
- Kanban (9)
- People (9)
- Business Architecture (8)
- Communities of Practice (8)
- Continuous Integration (7)
- Business Case (4)
- Enterprise Analysis (4)
- Angular UIs (3)
- Business Rules (3)
- GitHub (3)
- Java Development (3)
- Lean Startup (3)
- Satir Change Model (3)
- API (2)
- Automation (2)
- Scaling (2)
- Security (2)
- Toggles (2)
- .Net Core (1)
- AI (1)
- Diversity (1)
- Testing (1)
- ✨ (1)
- August 2024 (1)
- February 2024 (3)
- January 2024 (1)
- September 2023 (2)
- July 2023 (3)
- August 2022 (4)
- August 2021 (1)
- July 2021 (1)
- June 2021 (1)
- May 2021 (1)
- March 2021 (1)
- February 2021 (2)
- November 2020 (2)
- September 2020 (1)
- July 2020 (1)
- June 2020 (3)
- May 2020 (3)
- April 2020 (2)
- March 2020 (8)
- February 2020 (1)
- November 2019 (1)
- August 2019 (1)
- July 2019 (2)
- June 2019 (2)
- April 2019 (3)
- March 2019 (2)
- February 2019 (1)
- December 2018 (3)
- November 2018 (3)
- October 2018 (3)
- September 2018 (1)
- August 2018 (4)
- July 2018 (5)
- June 2018 (1)
- May 2018 (1)
- April 2018 (5)
- March 2018 (3)
- February 2018 (2)
- January 2018 (2)
- December 2017 (2)
- November 2017 (3)
- October 2017 (4)
- September 2017 (5)
- August 2017 (3)
- July 2017 (3)
- June 2017 (1)
- May 2017 (1)
- March 2017 (1)
- February 2017 (3)
- January 2017 (1)
- November 2016 (1)
- October 2016 (6)
- September 2016 (1)
- August 2016 (5)
- July 2016 (3)
- June 2016 (4)
- May 2016 (7)
- April 2016 (13)
- March 2016 (8)
- February 2016 (8)
- January 2016 (7)
- December 2015 (9)
- November 2015 (12)
- October 2015 (4)
- September 2015 (2)
- August 2015 (3)
- July 2015 (8)
- June 2015 (7)
- April 2015 (2)
- March 2015 (3)
- February 2015 (2)
- December 2014 (4)
- September 2014 (2)
- July 2014 (1)
- June 2014 (2)
- May 2014 (9)
- April 2014 (1)
- March 2014 (2)
- February 2014 (2)
- December 2013 (1)
- November 2013 (2)
- October 2013 (3)
- September 2013 (2)
- August 2013 (6)
- July 2013 (2)
- June 2013 (1)
- May 2013 (4)
- April 2013 (5)
- March 2013 (2)
- February 2013 (2)
- January 2013 (2)
- December 2012 (1)
- November 2012 (1)
- October 2012 (2)
- September 2012 (3)
- August 2012 (3)
- July 2012 (3)
- June 2012 (1)
- May 2012 (1)
- April 2012 (1)
- February 2012 (1)
- December 2011 (4)
- November 2011 (2)
- October 2011 (2)
- September 2011 (4)
- August 2011 (2)
- July 2011 (3)
- June 2011 (4)
- May 2011 (2)
- April 2011 (2)
- March 2011 (3)
- February 2011 (1)
- January 2011 (4)
- December 2010 (2)
- November 2010 (3)
- October 2010 (1)
- September 2010 (1)
- May 2010 (1)
- February 2010 (1)
- July 2009 (1)
- April 2009 (1)
- October 2008 (1)