This is how I think, build, decide, learn, and operate.

Ways into the operating system. Not widgets — a table of contents for how the practice runs.

1. 01

   Current Focus

   The workstreams that set the week — and the published cases behind them.

2. 02

   Method to evidence

   Four contribution groups from Work — each with a working method and one or two published examples.

3. 03

   Products as practice

   Small products are where the operating system meets real constraints—users, scope, trust, and shipping.

4. 04

   Decision Log

   Trade-offs that stayed — context, cut, outcome, lesson.

5. 05

   Experiments

   Hypotheses in motion: audio-first stories, constraint as editor, modular finance.

6. 06

   Writing and field notes

   Notes on decisions, trust, and operating models — browse on Notes, not here.

7. 07

   Archive

   Enterprise systems and earlier work that still inform how the OS runs.

The same contribution groups as Work. Method first — then one or two published examples.

• Product & 0→1

  Share one operating model across surfaces so new work joins the system instead of restarting the product.

  • EQTY →
  • Sagacito →
  • Shuttl →

• Founder-Built Products

  Ship the smallest useful version under real users; let constraint and trust edit the feature list.

  • GWK Ghostwriter →
  • Bolo Buddy →

• Leadership & Enterprise

  Align product, design, and operations on one decision path when the organisation is the constraint.

  • Rapipay →
  • Crowley →

• Additional / Earlier Work

  Earlier systems and brand work that still inform how product decisions get made.

  • Verizon →
  • Hempel →

Small products are where the operating system meets real constraints—users, scope, trust, and shipping.

• Can a founder run research-to-post with memory and voice rules — without a content team?

  GWK Ghostwriter

  Shipped workflow becomes the test: long-term memory, source material, and a voice that holds under deadline.

  Open published evidence →

• What survives when constraint edits the product — one audience, one promise?

  Growing With Kid

  Newsletter and community before a feature catalogue. The OS learns to cut theatre and keep the job.

  Open published evidence →

• Will trust hold when the interface disappears at bedtime?

  Bolo Buddy

  Audio-first, screen-free stories in languages that feel like home. Distribution is harder; the practice is clearer.

  Open published evidence →

• Can experience architecture live inside the operating system — not after the marketing site?

  EQTY

  Modules, states, and operator language before a campaign surface. The partnership tests whether quiet hierarchy scales.

  Open published evidence →

• Can a small brand stay honest when scale pressure asks for louder claims?

  Urban Prakriti

  Positioning and D2C for city residents. Still running — still teaching how a venture refuses commodity noise.

  Open published evidence →

1. 01

   Start with evidence

   A screen is only the surface. The review starts with the decision the user must make, and what could make that decision fail.

2. 02

   Make thinking visible

   Write the decision, the trade-off, and the lesson where the team can see them — or politics fills the gap.

3. 03

   Build systems, not dependencies

   If the work cannot run without you in the room, it is not a system. The deliverable is what generates the artefacts.

4. 04

   Ship useful versions early

   The smallest thing that answers who it is for, what they must decide, and what would make them stop trusting you.

5. 05

   Teach what works

   Students and teams are the fastest feedback loop. Teaching checks whether the bar travels without you.

Process and trade-offs. No invented results — only what the work taught.

1. 01 / Bolo Buddy

   Read entryClose

   Build bedtime stories as audio-first and screen-free, not as another kids’ app.

   Context

   Indian parents wanted culturally rooted stories. Existing platforms were Western-focused, screen-dependent, or mass-produced without cultural personalization.

   Trade-off

   Less visual theatre. Harder distribution in an app-store world that rewards screens. More work on voice, language, and trust.

   Outcome

   The product is defined by listening, not by a feed. Family voice-narration became a core idea rather than a feature bolted on.

   Lesson

   Children deserve tools built for them. Scaling an adult product down would have been faster and wrong.

2. 02 / Growing With Kid

   Read entryClose

   Let constraint edit the product — one job, not a catalogue of parenting features.

   Context

   Parenting advice is fragmented and overwhelming. A full app stack would have looked more ‘complete’ and said less.

   Trade-off

   Fewer surfaces to market. No theatre of process. The product has to be useful in a newsletter and a conversation first.

   Outcome

   The community product stayed small on purpose: essays, guides, programs — one voice, one audience, one promise.

   Lesson

   When the budget cannot buy another layer of process, the product has to say one thing well. That is still product work.

3. 03 / EQTY

   Read entryClose

   Join as founding design partner and treat experience architecture as part of the operating system.

   Context

   Financial products fail when trust, workflow, and business architecture are designed as separate layers.

   Trade-off

   Slower visible UI. More time in modules, states, and operator language before a marketing surface exists.

   Outcome

   The work is structured as a modular OS — how money, people, and decisions move — so new surfaces can join without a redesign each quarter.

   Lesson

   High-trust financial work is a workflow and language problem. The visual system stays quiet so the architecture can carry the product.

4. 04 / IIAD

   Read entryClose

   Teach design through decisions and production-bar critiques, not decoration.

   Context

   Studio traditions still reward polish. Practice now asks for systems, AI literacy, and the ability to defend a choice under constraint.

   Trade-off

   Less time on tool fluency as the headline. More discomfort in the room when a student cannot narrate the trade-off.

   Outcome

   Modules run as sprints. The critique is the curriculum: what they cut, what they kept, and what evidence moved the call.

   Lesson

   If juniors cannot apply the bar without a principal in the room, it is not a system. Teaching is how the operating model is checked.