Share this
The future of IT business analysis – moving from ‘what the business needs’ to ‘what the customer needs’
by Kirsten Eriksen on 13 July 2016
I can’t remember the last time I interacted with a real person at the bank for a “normal” transaction. Digital Transformation is here, and further along than we might realise. As the world continually evolves around us, we must also evolve to stay relevant.
One of our key tenets as Business Analysts is to always understand WHY things need to change, identify WHAT needs to change, and ascertain HOW we will deliver that change. In this post, I take a look at how Business Analysis has evolved and what Digital Transformation means for those of us working as BAs in the IT systems space.
Way back, before we Business Analysts existed, projects used Analyst Programmers to analyse and develop business solutions. While many of these people were no doubt excellent, there was always the risk of projects delivering what the Analyst Programmer thought the business wanted, or what the loudest voice in the room thought was important. The world realised this was a hit and miss way to decide what should be delivered, and the Business Analysis profession was born.
Business Analysis 1.0 – Delivering what the business needs, after they needed it
Ah, the days where we took 6 months to really understand the problem to be solved, and spent what felt like forever writing giant requirements documents.
During this time, we worked with business representatives and subject matter experts to elicit an understanding of ‘what the business required’. The business representatives or subject matter experts were normally people who worked in the business and who brought a deep understanding of the subject.
The problem wasn’t so much WHAT we were doing but HOW we were doing it. These projects took a long time to deliver anything tangible, and as we now know, in the interim the business moved on, and often, what was being delivered no longer met the business needs due to that time delay. In order to succeed in this environment, it required extremely good direction setting and a slow changing business environment; which are both simply unrealistic expections.
Business Analysis 2.0 – Delivering what the business needs, when they need it
In a fast changing world, the business analysis discipline has adopted Agile and Lean techniques to encourage changing needs and to continuously re-prioritise to deliver what the business requires right NOW.
Our time and budget is now focussed on delivering the highest value for the business first. We’re still working with the same people in the business, but delivery is quick, meaning that the business gets what it needs when it needs it.
The ability to change when needed has become an asset to businesses. Being set up to facilitate continuous delivery allows a business to move and flex, and be responsive to the ever changing external and internal needs of the business.
Business Analysis 3.0 – Delivering what the customer needs, when it suits them
Our world is changing again with disruptive new business models and accelerating customer expectations driven by technologies such as social, mobile, analytics, cloud and internet of things (SMACIT). This again means we need to change how we look at our Business Analysis world in order to stay current.
Digital transformation projects are taking the ‘business’ out of ‘business systems’ and making them ‘customer systems’. Customers want to be able to do what they need to, when they need to.
Banks have really embraced this change. Today, if you need to make a bank transaction, you don’t deal with a bank teller for them to organise the transaction in their ‘business system’. You jump on your banking app ‘customer system’ and do it yourself.
More businesses are jumping on this, and we need to be ready for the switch, and in some cases guide the business towards it, as “you don’t know what you don’t know” – if they don’t know there’s a better way, they can’t consider it.
What does Business Analysis 3.0 mean for business analysts?
We can no longer rely solely on business representatives, subject matter experts or product owners. They understand their business requirements and we’ll still need to work with them on those, but do they really know what their customers need from the customer system? They might think they do, but business success may well depend on getting it right, so we should be talking to the customers to make sure.
The techniques for understanding customer requirements aren’t that different to those used for business requirements. The change will be in the need to build up what I call “Companion Skills”, like market research, customer experience and design thinking.
Potential frameworks, approaches and techniques may include (but won’t be limited to):
- Customer Experience/Journey Mapping
- Design Thinking
- Service Blueprints
- Heuristic Evaluations
- The 3 G (Gemba, Gembutsu, Genjitsu) Approach
- Continuous Improvement
- Simplification
- Situational Analysis
Personally, I think Business Analysis 3.0 has been a long time coming. I’m excited for the change this will bring to the profession, and therefore to customers. There will be more change to come, this industry and the profession of Business Analysis is one that will always evolve. For me, this keeps things interesting and means that I continue to learn and grow.
Kirsten Eriksen is a Senior Consultant specialising in business analysis, based in Equinox IT’s Wellington, New Zealand office.
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)
- Cloud (26)
- Digital Transformation (26)
- Project Management (26)
- Azure DevOps (23)
- Coaching (23)
- IT Governance (23)
- System Performance (23)
- Innovation (21)
- Change Management (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)
- AI (2)
- API (2)
- Automation (2)
- Scaling (2)
- Security (2)
- Toggles (2)
- ✨ (2)
- .Net Core (1)
- Diversity (1)
- Microsoft Azure (1)
- Testing (1)
- December 2024 (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)