The thinking, not the marketing.
Writing about business problems and how they actually get solved. The bar for publishing anything here is that it has to be useful to someone who never gets in touch.
Nothing published yet
This section is empty on purpose.
A new consultancy’s blog is usually six articles written in one afternoon to make the section look inhabited. They are recognisable within a paragraph, and they cost more credibility than the empty page they replaced.
So there is nothing here until there is something worth reading. What the section will cover is below, and it is real: these are the subjects the work actually turns on and the questions that come up in most first conversations.
What gets written about.
Eight subjects, each one drawn from work rather than from a keyword list.
- Business problems
- Diagnosing what is actually wrong, in plain English.
- Process improvement
- How work really moves, and where it stalls.
- Solutioning
- Choosing between buy, build, integrate and automate.
- Software and engineering
- What it takes to build something that lasts.
- Product
- Turning a vague need into something buildable.
- Technology strategy
- Connecting technology decisions to business goals.
- Founder perspective
- What running the work teaches that reading about it does not.
- Digital platforms
- Websites and portals as systems rather than pages.
The recurring series.
Most pieces belong to one of these, which is what stops a blog becoming a pile of unrelated posts.
Business Problem of the Week
One business problem, diagnosed in plain English, with the options laid out.
Buy / Build / Integrate / Automate
A real decision worked through, including why the other three lost.
What I Would Change
A workflow or a digital journey, analysed as if it were an engagement.
Requirements That Matter
The business-analysis thinking that decides whether a build lands.
Field Notes
Lessons from real projects, with nothing confidential in them.
From Problem to Product
How a vague need becomes a specification and then working software.
Every piece follows the same path.
The same path an engagement follows, which is not a coincidence: a piece of writing that cannot get from a problem to a recommendation was not worth publishing.
- Problem
- Why it happens
- How to diagnose it
- Options
- Recommendation
The questions this is being written to answer.
Not a publishing schedule — a list of what actually gets asked. If one of these is your question, it is worth asking directly rather than waiting for the article.
- When has a business outgrown spreadsheets?
- Buy, build, integrate or automate — and how to tell which
- How to know whether a process actually needs automation
- Why software projects go wrong before development starts
- How to turn a business problem into software requirements
- What a good solution blueprint actually contains
- When should a small business build custom software?
- How to map a broken workflow
- What an IT roadmap should actually contain
- When a customer portal makes sense
- Why process improvement should come before AI