Context

Fifteen ministries and departments published real problem statements; final-year engineering students across the country built winning solutions against them. The political intent was explicit: departments would adopt the winning innovations into their systems.

The operational reality: nothing existed between the podium and the department. Everyone was designing the event. Nobody owned what came after it.

The failure modes, diagnosed before designing

Engaging stakeholders across all fifteen departments, the colleges and the students surfaced failure modes that were structural, not logistical.

• The lifecycle mismatch. Government integration (rigorous testing, security checks, compliance) takes one to three years in a department like ISRO. The builders were final-year students who would graduate mid-integration.
• The continuity gap. When the original student leaves, who carries the project without restarting the compliance clock?
• Six plausible IP claimants. Nobody had decided whose innovation this was.
• The bandwidth conflict. Students building government systems while completing coursework.
• The funding vacuum. Nobody had named who pays.

The builderFinal-year student

The integrationTesting, security, compliance

Award1 year2 years3 years

The six people who could each claim the innovation:

Designing for the binding constraints

The framework had to survive the strictest compliance regime and the shortest participant tenure, simultaneously. If it worked for ISRO's three-year cycle and a graduating student, it worked everywhere.

Two more principles followed. Each department had to be able to adopt the framework without renegotiating its own internal rules, or it would die in committee fifteen separate times. And the ownership questions went on the table at kickoff, while goodwill was highest and resolution was cheapest.

The result was the Post–Smart India Hackathon operational framework: continuity and handover between student cohorts; roles across nodal officers, mentors and institutions; the IP position; funding; and a compliance-aware timeline honest about government integration cycles. I drafted it, and negotiated it across fifteen secretariats with fifteen different rulebooks.

What changed

The framework was rolled out and executed at national scale for the first edition, and the intent became operational reality: student projects were incorporated into departmental systems. An initiative that had a podium got a pipeline.

Context

At the heart of BT's client engagement lies the Configure, Price and Quote (CPQ) journey: the critical component in securing new business and keeping existing relationships alive. This is the story of transforming it, fought on two fronts: the global sales process at large, and its hardest proving ground, CPE Resale, a £120M+ hardware line where the gap between strategy and reality was widest.

The legacy labyrinth

My first task seemed simple enough: map the existing CPQ process. I quickly realised I was staring into undocumented workflows, each product line with its own approach, built on years of unwritten rules and institutional knowledge.

How do you map something that exists primarily in people's heads?

So I interviewed sales users and stakeholders across product lines. A jigsaw without a picture on the box, each conversation adding a piece to the landscape of the legacy journey.

The blueprint that nobody used

Armed with hard-earned insights, I built a comprehensive service blueprint on Mural. I thought I had cracked it. Weeks later I noticed something odd: nobody was using it. A quick survey found two barriers: limited Mural licences, and the overwhelming complexity of the artefact itself.

So I translated the blueprint into a tabular, Excel-based document. Less beautiful, universally accessible. It was widely adopted, regularly updated, and became a living repository of organisational memory for the legacy sales journey.

The proving ground: the 2% discovery

Understanding the landscape is one thing; changing it needs a beachhead. CPE Resale supplied one, in a single brutal statistic.

2%of roughly 8,800 offers a year were even eligible for the strategic quoting journey. 95.5% of revenue still ran through the legacy process.

Not hostility; exhaustion. The brief said "improve the tool's usability", but usability polish assumes the destination is right and only the ride is rough. I reframed: why can only 2% of the business use the strategic journey at all, and can the sanctioned direction ever serve it?

I mapped the as-is at task grain (stage, frequency, owner, tools, process time, waiting time, and critically how many times data gets re-keyed), turning "the journey feels heavy" into a measurable quantity: 35 screens, propped up by four Excel side-tools. Root-causing the eligibility failure showed 68% came from one structural blocker: legal entity data unavailable. This was never a training problem.

Charting the future

Alignment came in two intensives. A three-day workshop with business leaders, sales representatives and technical experts produced a roadmap, guiding principles and evaluation metrics for the wider transformation. A three-day design sprint, run in relay between India and the UK, took the proving ground deep: process flow and root-cause analysis, storyboarding, then Prototype 1.0 with a trial run. With a Business Analyst and a Systems Architect, we crafted the to-be blueprint through countless whiteboard sessions and heated debates.

The three-way test

Then the move that made this different from the three discovery efforts before it. I scored every pain point on the evidenced register against three options side by side: the as-is journey, the strategic-tool journey, and a redesigned journey.

So I recommended against the sanctioned direction: a contextually aware guided journey, and a formal proposal for an alternative quoting journey. Saying no to a signed-off strategy is expensive; the comparative table meant the evidence took the hit instead of a person.

From concept to reality

Leading a design team on the clickable prototype, we tested with sales users, gathered stakeholder feedback and refined, round after round. As implementation approached I became the mediator between design aspiration and technical reality, learning to defend design choices with conviction while staying open to technical feedback.

Measuring success

Before: 35

After: 13

Behind the numbers: improved customer satisfaction, more bid-to-order conversions, a stronger revenue funnel, and the direction itself changed as the business began building the alternative quoting journey.

What I carry from this

Adapt the artefact to the audience. A blueprint nobody opens is a service that never happened. Say no with conviction and rationale. A transparent test anyone can attack turns career risk into design leadership. Human-centricity is a mindset, not a deliverable. It has to reach every decision, including the unglamorous ones about Excel.

Context

It began with a job-interview assignment. What seemed like a standard task became a passion project, one that led me, quite literally, to the doors of the National Museum. The challenge: make museums more appealing to India's youth.

Starting with the history

I began with the essence of the thing itself, tracing "museum" to its Greek root, mouseion, a seat of the Muses, and following the idea from Roman times to the present. Museums have moved from places of preservation, to spaces of exhibition, to what they are becoming now: a medium for experiencing our past.

Casting the net wider

I researched global initiatives in museum technology, the pros and cons of digitalisation and the tools museums use worldwide, then mapped the ecosystem itself: the web of visitors, researchers, curators and government officials that keeps these institutions alive.

Boots on the ground

Theory only goes so far. I visited the Rashtrapati Bhawan Museum and the Red Fort Museum in Delhi, observing visitors and the state of digital integration, and interviewed a deliberately diverse group: a National Museum official, a curator, representatives from the Bihar State Museum and the Government of India, and a teacher leading a school trip. Then an International Conference on Reimagining Museums in India, hosted by the Ministry of Culture, offered wider perspective and validated many of my findings.

What the research said

• Stories are missing. Objects sit labelled, not narrated.
• Data collection is limited, hampering informed decisions.
• Accessibility is routinely overlooked, with barriers the spaces were never designed around.
• Ambition outpaces operations. New museums struggle to maintain state-of-the-art equipment.
• Visitor fatigue is real. Sensory overload and a lack of seating shape the experience as much as the exhibits.
• The visit is not the relationship. Community participation, links with education, and engagement before and after the visit are what sustain a museum.

Visitor-motivation research gave the work its segmentation lens:

Personas

Defining the challenge

How might we bring culture, heritage and museums into the mainstream consciousness and educational discourse of society?

With that North Star set, I ideated across four fronts: spatial and experience design, communication strategy, integration into school curricula, and technology for management and visitor experience. Each concept traced back to the insight that earned it. What began as an interview assignment ended as an informal pitch to National Museum officials.

Context

A migration to the strategic stack was already in flight. But the fulfilment journeys it was migrating lived in people's heads and in Excel: undocumented, undesigned, and treated as inherently bespoke, so every improvement was a one-off and nothing compounded. The programme was committing build capacity against a journey no one could draw.

The brief said: document the corporate and public-sector fulfilment journey. But documenting a broken thing gives you a well-drawn broken thing. I reframed to the diagnostic question: why does it break, and what is actually different from SMB? The answer became a thesis.

Proving it

Four axes (segment, service model, product type and configuration complexity) replaced "corporate is just complex" with a testable model of where complexity actually lives. Every claim in every artefact was badged as sourced, inferred or extrapolated, and traced to pain IDs, tickets or transcript quotes.

And the gaps stayed gaps. Customer personas and an emotional journey graph were deliberately not authored, because the research behind them hadn't happened yet.

The as-is went deep: a blueprint of the wrapper itself, sixteen ecosystem blueprints of the delivery stage, and a nine-family catalogue of the bespoke forks. It proved the bespoke surface was small and the shared engine large. The "every order is unique" assumption did not survive contact with the catalogue.

The problem, quantified

These orders ran on the same order engine as small-business orders, wrapped in a layer of manual work: re-keying, spreadsheets and chasing, done by hand by managed-service teams and order managers. Fix that layer and most of the pain goes with it. Scroll through the 87 to see them gather.

Thirty-six unhappy scenarios were consolidated into twelve recovery blueprints, because a service is defined by how it fails. One finding reset the programme's intuition: 38 to 40% of fulfilment delay traced to a single stage, order enrichment, hiding in plain sight.

Answering it

Sixteen journey patterns plus ten micro-pattern components, each framed as a Job to be Done: define once, compose any journey. A deliberate departure in method: micro-patterns are specified interface-first (trigger, inputs, outputs, canonical flow), not as swim-lane blueprints, because components aren't journeys.

The future state was traced, not asserted: eleven experience principles, each with a litmus test; a North Star of order observability with a progressive control ladder; and to-be blueprints, a 23-stage end-to-end journey and a 26-task corporate blueprint, where every capability traces from pain to resolution to delivery ticket.

165backlog tickets mapped

14delivery blocks

29ticketed quick wins, the lowest-uncertainty start

Decisions, and what they cost

• Augment the order manager; don't automate them away.A senior design lead challenged the automation direction: past a point, a great order manager is the relationship. The evidence agreed in part. Automate the mechanical layer, protect the relational one.
• A pattern system over bespoke fixes.Slower to first value, in exchange for a design system where every journey compounds the investment.
• Depth before coverage.Corporate fulfilment went to full design depth first, including all twelve failure-recovery paths, because that's where migration risk concentrated.
• Honest gaps over confident fabrication.Two expected artefact types were refused rather than invented. It built more trust than completeness would have.

What changed, honestly tiered