Date: 30 - 30 Mar 2023

How can we tell a story through Business Analysis? Capco is pleased to share insight into how we take our stakeholders along on a journey as we analyse their processes, requirements, solutions and functionality. In this webinar we will share how we bring together various approaches, techniques and artefacts to ensure the analysis is well connected and appreciated across the full delivery lifecycle. We will also explore:

  • Why do we tell stories
  • The stories told by Business Analysts
  • Bringing the BA story to life for clients and other stakeholders


John Wisner
Managing Principal, UK Consulting BA and Process Excellence Lead, Capco

Speaker Bio:

Managing Principal and the UK Consulting Lead for Business Analysis and Process Excellence, as well as Global BA training Lead.

John was the IIBA UK Business Analyst of the Year Finalist in 2022. He has 20+ years business analysis and transformation experience leading teams in Financial Services, as well as extensive skills in digital transformation, functional architecture, Software Development Life Cycle (SDLC) best practices, designing Know Your Customer (KYC) Target Operating Models and more.

Headshot of John Wisner

Some further responses to questions we did not get to in the session are below:



How might we capitalise on storytelling to showcase the value co-created by business analysis?

We initially tell the story of our analysis, focused on business and beneficial outcomes, for our respective projects or project stakeholders. We often look for opportunities to share this more widely with interested parties (perhaps our LinkedIn network), teams and centres of excellence (i.e. our BA centre of excellence). Sharing in this way helps further in raising or maintaining the awareness of the value of business analysis.

How to make our story Climax more interesting?

To make a story more interesting to an individual it has to resonate and be relatable to them. Therefore, by considering who is going to receive and benefit from the information we share, we can tailor or pitch it appropriately. Bringing personal experiences (i.e. of the teams or clients involved) or real-life situations, can also help. We try to also leave our stakeholders with a very clear idea of the most relevant and important points. Finally, we can use more interesting ways to deliver or visualise our analysis (i.e. animations, graphs, Gifs etc).

During the requirements validation phase, what techniques do you use to play back the requirements?

Whatever technique we use, it is important that we do not alter the requirement so that they differ from its intended end state. However, we always try to make each requirement concise and relatable, affiliated to processes or other related BA model. If the requirements relate to a specific phase in the process or features/components in the solution, grouping and displaying the requirement and model together might help. We also aim to focus on the highest priority items first.

Any top tips around traceability and documenting the story throughout the project?

Ensure traceability is considered from the outset and updated/recorded as your analysis progresses. Keep it transparent and treat your traceability matrix as a product. Doing so will help consider the audience, presentation and usability. Also, don't forget that traceability extends to all disciplines across change, so ensure you engage development, vendors, architects, process teams, the BAs and the business. The full matrix needs to be connected or connectable to ensure the view of traceability is comprehensive.

How we use storytelling to deliver our deliverables?

We use a lot of visualisation techniques, diagrams, models and infographics. From a wide-ranging toolkit, we look to select those most appropriate based on the change/project, stakeholders, client, situation and available tooling. We ensure the deliverable is both obvious and central to the specific story.




To join the discussion, please sign in.