From problem to release

How I run an e-commerce project

Every engagement is different, but the route should remain easy to follow: understand the problem, decide what to do and verify that the solution works.

1
Work out whether I can help
In the free 45-minute first call, we discuss the problem, what you have already tried and the constraints we cannot ignore.
2
Define the actual work
I review the systems, data and people involved. When there is more than one route, I compare the consequences, risks and ongoing costs.
3
Agree the scope
We define what is included, what is outside the engagement, who owns each responsibility, the priorities and what we need to see before the work is considered complete.
4
Work in verifiable steps
I share progress and problems before the end. Where possible, I release small pieces so the team can test them and adjust the direction.
5
Release without leaving a mess
We check the important scenarios before going live. After release, I hand over the documentation, access and instructions needed to run what was built.

When making decisions: I prefer a solution that is straightforward to maintain over an architecture that is more sophisticated than the problem requires. Security, performance and operating cost are part of the decision from the start.

In day-to-day work: few meetings with a clear purpose, written updates and recorded decisions. You should know what is happening without having to chase the project.

Have a project that needs clarity?

Tell me where you are, what is not working and which decision you need to make. In the first call, we can work out whether and how I can help.

Let’s talk