Insights
Writing about work, making, design and technology, with examples and questions worth revisiting.
Writing archive
PrototypingBuilding as a way to test assumptions
How a simple prototype can make an assumption observable.
Which assumption should the prototype make observable?
Read the piece1 min read
DesignGood design makes understanding easier
In interface design, beauty can help clarify relationships, priorities and the next step.
What should the reader understand first, and what comes next?
Read the piece1 min read
BrandingRebranding in the age of AI: beyond generating images
AI can generate more options. Positioning, recognizability and responsibility for publishing still require judgment.
Read the piece4 min read
BrandingA brand is a promise kept in practice
Visual identity makes a promise visible. Buying, support and delivery show how real that promise is.
Read the piece4 min read
Reading path 10 / 10Digital transformationDigital transformation needs a rhythm, not a finish line
After launch, a different kind of work continues: observing outcomes, choosing the next improvement and preserving the ability to change.
Read the piece4 min read
Reading path 9 / 10Digital transformationDigital change is a team effort
New software becomes part of real work when understanding, authority, practice and support come together.
Read the piece4 min read
Reading path 8 / 10Digital transformationClarify the problem before choosing AI
A useful AI application starts with a real decision and its constraints, not an appealing model or a promise to do everything.
Which decision needs to improve before we choose a model?
Read the piece4 min read
Reading path 7 / 10Digital transformationClarify the data before building the dashboard
A precise chart cannot clarify ambiguous data. Establish definitions, quality and ownership before designing the display.
Read the piece4 min read
Reading path 6 / 10Digital transformationSometimes the best automation removes a step
Before making a task faster, understand why it exists. Then decide whether to remove, simplify or automate it.
What does this step control, and is it still needed?
Read the piece4 min read
Reading path 5 / 10Digital transformationHow do we know whether a change helped?
Separating activity from outcomes, establishing a comparison and noticing effects hidden behind successful-looking numbers.
Read the piece4 min read
Reading path 4 / 10Digital transformationWhich change should come first?
Prioritizing through impact, evidence, uncertainty and readiness, rather than the appeal of a proposal.
Read the piece3 min read
Reading path 3 / 10Digital transformationMap the service, not just the organization chart
From the initial need to the outcome: seeing touchpoints, backstage work and the connections where a journey breaks down.
Read the piece4 min read
Reading path 2 / 10Digital transformationUnderstand the problem before choosing a solution
Moving from a vague request for a new tool to a clear account of the person, situation, obstacle and consequence.
Read the piece4 min read
Reading path 1 / 10Digital transformationDigitizing is not always an improvement
The difference between a new tool and better work: why an online form alone does not fix a process.
The tool has changed. Has the work improved too?
Read the piece4 min read