Approach

How I Work

Start with the problem. Work out what matters. Make something happen.

You don't need to know what technology you need - or even have completely defined the problem.

Bring me the challenge, opportunity or slightly uncomfortable "we really ought to do something about this..."

From there, the way I work is pretty simple:

  1. 1

    Understand

    I'll get under the skin of the problem - talking to the right people, understanding what you already have and what you're trying to achieve.

  2. 2

    Prioritise

    We'll work out what matters, what's possible and what's actually worth doing.

  3. 3

    Do

    If something is worth pursuing, we'll make it happen - whether that's a quick experiment, a focused project or something more substantial.

  4. 4

    Review

    We'll measure what happened, learn from it and decide what to do next.

  1. Understand
  2. Prioritise
  3. Do
  4. Review

Sometimes that's the end of the job.

Sometimes one problem leads to another project.

And sometimes it makes sense for me to stay involved as your Fractional CTO - providing ongoing technology leadership for a few days each month.

There's no conveyor belt. You use me for as much - or as little - as makes sense.

We start with the problem, not the technology.

Before recommending anything, I need to understand your organisation.

I'll spend time with you and the people who actually do the work. I'll look at the systems and technology you already have, how your data is being used, where the frustrations are, what's already working and what you're trying to achieve.

This isn't an enormous consultancy discovery exercise.

It's enough investigation to make sure we're solving the right problem.

I don't start from a blank sheet of paper.

I've developed practical ways of getting to the heart of an organisation quickly.

Depending on the problem, I can draw on technology and AI reviews, structured staff interviews, supplier and systems reviews, data and security assessments, and other diagnostic approaches to quickly build a picture of what's going on.

And because I've spent years working in the cultural sector, I already know many of the systems, suppliers and challenges I'm likely to encounter.

That means we can spend less time explaining the landscape and more time working out what to do about it.

Where I don't know something, I'll say so - and find out.

The point isn't to put you through a standard consultancy process.

It's to get to useful quickly.

Then we work out what matters.

There will almost always be more things we could do than things we should do.

We'll identify the opportunities and problems that matter most and work out where technology could genuinely make a difference.

Some things might be quick wins. Some might need a focused project. Some might need investment or organisational change.

And some ideas we'll decide aren't worth pursuing at all.

Knowing what not to do is part of the job.

The result is a practical set of priorities and clear next steps - not a technology wishlist.

Then we make something happen.

Once we've decided something is worth doing, we'll find the simplest sensible way of moving it forward.

That could mean fixing something that's getting in the way, choosing or connecting technology, changing a process, creating an AI workflow, improving how you use data or working with one of your existing suppliers.

Or sometimes the best way to answer a question is simply to build something small and see whether it works.

I like getting from "we should..." to "we did."

Move quickly. But responsibly.

Good technology decisions aren't just about whether something can be done.

We also need to ask whether it should be done, what could go wrong and how we protect the organisation and the people whose data we hold.

I've worked extensively with GDPR and data protection throughout my career, and where personal data is involved I prefer to build privacy in from the beginning rather than bolt it on afterwards.

I'll also consider the wider security implications of what we're doing: what data we're using, where it goes, who should have access to it, how systems are protected and what new risks we might be introducing.

For significant decisions, we'll identify and assess those risks rather than simply hoping for the best.

Innovation and good governance aren't opposites.

Done properly, governance gives us the confidence to move faster.

Start small. Learn. Then decide.

Particularly with new technology, I don't believe every good idea needs to begin with a business case, a twelve-month project and a large budget.

Sometimes we can test an idea quickly.

Build a prototype. Try a workflow. Run an experiment. Put something in front of real people.

Then we learn.

If it works, we build on it.

If it doesn't, we've learned something without betting the farm.

Progress beats theoretical perfection.

I'll work with your people, not around them.

Fractional doesn't mean parachuting in and taking over.

The people in your organisation understand it better than I ever will. Your existing suppliers and technology partners may also have years of valuable knowledge.

My role is to bring another perspective, ask the difficult questions, connect things together and help everyone move in the same direction.

Where specialist expertise is needed, I'll help identify it and work alongside it.

The aim is to increase your organisation's capability, not make it dependent on me.

You'll know what we're trying to achieve.

Technology projects have an unfortunate habit of becoming about delivering the project rather than achieving the outcome.

So we'll agree what success looks like.

We'll establish sensible milestones.

And we'll keep asking a simple question:

"Is this actually making things better?"

If the answer stops being yes, we change course.

The easiest way to start is a conversation.

You don't need a brief.

You don't need a technology strategy.

And you definitely don't need to decide which of my "services" you want.

"Surely there must be a better way of doing this?"

And we'll start there.

Talk to Stu