How 3Clicks Works

Fixing SharePoint isn’t a project you commission and walk away from. Here’s how I work.

Every organisation is different. The problems look similar on the surface , staff can’t find things, information is duplicated, nobody quite trusts the system , but the causes, the culture and the constraints are always specific. That’s why I don’t arrive with a pre-packaged solution. I arrive to understand.

Stage 1: Discover

It starts with listening, not presenting.

Before I touch anything, I want to understand how your organisation actually uses information , not how it’s supposed to work on paper, but how it works in practice. That means talking to staff at different levels, not just the people who commissioned the review.

Often this is the most valuable part of the process. Staff usually know exactly where the friction is. They’ve just never been asked , or they’ve asked themselves and nothing changed. A few structured conversations typically reveal the same pain points coming up repeatedly, and that pattern tells you where to focus.

This stage also means I’m looking at what you have: your current SharePoint structure, your document libraries, your naming conventions (or lack of them), your search experience, your navigation. I’m forming a picture of the gap between where things are and where they need to be.

What this looks like: A combination of structured conversations with staff, a review of your current information environment, and a clear written summary of findings and priorities. No jargon. No slide deck full of frameworks. A plain account of what’s working, what isn’t, and what I’d recommend doing about it.

Stage 2: Redesign (The Sprint)

Fixing it, properly.

With a clear picture of the problems, I rebuild. This is the hands-on work , restructuring navigation, rationalising document libraries, introducing consistent naming conventions, improving search, and making sure that the information people need most is the easiest to find.

The design principle throughout is simple: any document or resource your staff regularly need should be findable in three clicks or fewer. This forces every decision about structure to be made from the user’s perspective rather than the organisation’s internal logic.

This stage often involves some difficult decisions , archiving old documents, consolidating duplicates, retiring structures that no longer reflect how the organisation works. I’ll guide those decisions, but they’re made with you, not imposed on you.

What this looks like: Practical, visible changes to your SharePoint environment. Better navigation. A structure that reflects how your staff think, not how your org chart is drawn. Documents where people expect to find them.

Stage 3: Embed

Making it stick.

A rebuilt SharePoint that nobody understands how to maintain will drift back to where it started within a year. The final stage is making sure it doesn’t.

That means making sure your staff understand the new structure and can use it confidently. It means giving whoever is responsible for maintaining it the tools and the confidence to keep it ordered. It means being available as things evolve , because organisations change, and the information environment needs to change with them.

I don’t do this remotely or transactionally. I stay involved until I’m confident the change has taken hold.

What this looks like: Staff guidance (simple, practical , not a 40-page manual), a handover to whoever owns the system internally, and continued availability for questions and adjustments as things bed in.

What About Cost?

A transparent answer to an important question.

Engagements like this aren’t cheap if they’re done properly, and I won’t pretend otherwise. The Discovery stage alone takes time to do well. A rebuild , depending on the size and complexity of your organisation , is a meaningful investment.

I also understand that for many organisations in the VCSE sector, committing significant budget to something that feels like “IT” is a hard sell internally, even when the case for it is strong.

So here’s what I’d suggest if you’re interested but uncertain: Start with a Discovery conversation. A single structured session , a couple of hours , where I look at what you have, talk to a handful of staff, and give you an honest view of where you stand. That gives you something concrete to take back internally, and gives me enough to propose a realistic scope of work. It’s a low-risk way to find out whether the fit is right.

If the full engagement isn’t the right move right now, the Discovery output still has value. You’ll know where the problems are, which is more than most organisations do.

Who This Is For

3Clicks works best with organisations between roughly 70 and 250 people , large enough that information management is a real operational problem, small enough that the work can be done with the kind of personal engagement that makes it stick. Most of my work is with voluntary, community and social enterprise organisations: charities, membership bodies, community-focused groups. These are the places where the gap between what SharePoint could do and what it actually does is often largest , and where the impact of fixing it is most directly felt by the people the organisation exists to serve.

If you’re a larger organisation with a complex, multi-team SharePoint environment and a dedicated IT function, I’m probably not the right fit.