Thinking
in public.

Notes on business, product, data, CRM, systems, and the space between them. Making the reasoning as visible as the finished work.

Why Good Technology Projects Start With Business Questions

Teams often jump from a problem directly to a feature, platform, or automation. Technology becomes more useful when the decision it needs to improve is clear before implementation begins.

4 min read
Read the note

Inside this note

The best technical solution is the one that removes the right constraint with the least unnecessary complexity.

  1. 01

    Start with the outcome

  2. 02

    Find the real constraint

  3. 03

    Choose technology last

Business ↔ Technology

Data

3 min read

A Dashboard Is Not a Decision System

More metrics do not automatically create better decisions. A useful analytics system connects each measure to a question, the context needed to interpret it, and an action worth considering.

Read

CRM

5 min read

From Broadcasting to Lifecycle Orchestration

The difference between a messaging tool and a lifecycle operating model is not the number of channels. It is whether customer state, decision rules, and feedback determine what happens next.

Read

Analytics

4 min read

Why Predictive Analytics Must End in an Action

A predictive score is interesting only when it helps someone make a better decision. The useful output is not a number on its own, but a clear change in prioritisation, workflow, or experiment design.

Read

Architecture

5 min read

Designing Multi-Database Systems

Serving several organisations from one application can require more than an additional connection string. Data boundaries, migrations, observability, and operating responsibility all become architectural concerns.

Read

Engineering Operations

4 min read

Making Deployments Observable and Reversible

A production change becomes safer when the team can see what happened, decide whether the release is healthy, and return to a known state without improvising under pressure.

Read