Project 06 of 09 Professional work Transformation · Analytics · Capability
Changing how work gets done
An early chapter connecting analytics, Agile working practices and digital capability with business performance.
At a glance
An early chapter connecting analytics, Agile working practices and digital capability with business performance.
- Role
- Digital Transformation Consultant
- Period
- Jul 2014 – Aug 2015
- Focus
- Analytics, Agile practices, upskilling
- Base
- Mumbai, India
The remit
Change the decisions and the way they get made.
As a Digital Transformation Consultant at Reliance Group, I worked across analytics, development practices and digital upskilling. The role provided a foundation in the relationship between technology, people and business change.
A useful lens for this work is that transformation needs more than a tool: people need information they can use, a way to act on it, and the capability to sustain the change.
Analytics
Strengthen the basis for business decisions.
I strengthened analytics through an initiative contributing to 25% revenue growth.
That is a contribution to an initiative-level result. The available record does not isolate the effect of analytics from the other factors involved, so the outcome is presented with that boundary intact.
Ways of working
Make delivery cycles shorter.
I introduced Agile practices that shortened development cycles by 50%. This work concerned how development was organised and delivered, alongside the analytics initiative.
Shorter cycles describe delivery cadence. They should not automatically be read as a claim about software quality or customer satisfaction; those would require their own evidence.
Capability
Help people participate in the change.
I led digital upskilling, supporting a 35% improvement in workforce productivity.
Capability building worked alongside changes to tools and processes. Making the new ways of working understandable was part of making them useful.
Reflection
A first chapter in connecting disciplines.
This role brought analytics, delivery practices and capability building into one transformation remit. Those connections continue to inform how I approach product and experience leadership.
The work dates to 2014–2015. The illustrations on this page explain its themes rather than reconstructing historical internal systems.
Experience lens
From a signal to a change people use
A simplified way to read how customer insight becomes a decision and then a change people adopt. A model for reasoning about the work, not an account of a specific programme.
Illustrative service blueprint. An original model for exploring the experience across customer, service and operations.
| Signal | Decision | Adoption | |
|---|---|---|---|
| Customer What the person does | Shows needs through behaviour | Not in the room | Meets the change |
| Frontstage What they see and touch | Evidence readouts | Prioritisation and trade-offs | Roll-out and enablement |
| Backstage What makes it work | Collection and synthesis | Feasibility and business case | Process, tooling, measurement |
Stage 01 of 03 · The design question
Which signals are strong enough to act on?
- Customer Shows needs through behaviour
- Customers rarely state their needs directly. They show them in what they do, what they abandon and what they say when they are asked well.
- Frontstage Evidence readouts
- Signals only travel if they reach decision-makers in a form they can weigh: clear, honest about uncertainty and tied to a real customer moment.
- Backstage Collection and synthesis
- Gathering, cleaning and synthesising evidence is the slow work that makes a readout credible enough to act on.
Stage 02 of 03 · The design question
Who speaks for the customer when they are not in the room?
- Customer Not in the room
- Most decisions about customers are made without them. Their voice arrives second-hand, through the evidence someone chose to bring.
- Frontstage Prioritisation and trade-offs
- Making trade-offs explicit, what we will do, what we will not and why, is what turns evidence into a decision people can stand behind.
- Backstage Feasibility and business case
- Cost, effort and constraints shape what is possible. Surfacing them early keeps the decision honest.
Stage 03 of 03 · The design question
What has to change for people to actually use it?
- Customer Meets the change
- A change only matters once customers meet it in their own routine and find it genuinely better than what came before.
- Frontstage Roll-out and enablement
- The teams delivering a change need to understand it, believe in it and know how to use it before customers ever see it.
- Backstage Process, tooling, measurement
- Processes and tools have to change underneath, along with a way to see whether the change is actually being used.
Selected professional work. Diagrams are original explanatory models.