What Pathfinding is

Pathfinding is how a project starts at Animikii. Before anything is built, we spend a series of sessions with a client working out what they actually need, and whether building it is the right idea at all.

Often there is already a system in place, and a good part of the sessions goes on what it does well and what it gets wrong.

Often what they need is a community archive: somewhere to hold photographs, recordings, documents, and the stories attached to them.

It ends in a report the client owns outright, and that ending shapes everything before it.

Where I come in

The sessions are collaborative, and most of what comes out of them on the design side is mine. I work out the roles, write the user stories, draw the site map and the flows, and build the wireframes and the prototype the client clicks through at the end.

Working out the roles

Before it is a screen, a community archive is a question about access.

So that is where the sessions go first: how many kinds of user there are, and what each one is allowed to see. The client tells us what they need, and the roles and their permissions come out of that.

User stories

Once the roles are clear, the stories follow from them. I write them: what each kind of user needs to do, and what should happen when they try to do something they shouldn’t.

The roles and the stories go back to the client for approval. Nothing visual gets made until they are signed off.

Site map, flows, wireframes, prototype

With the roles and stories approved, the design work starts: the site map, the user flows, then wireframes, then a clickable prototype.

The prototype is where it stops being a document. The client clicks through it and sees what the thing would look like if it were built.

The report

Everything lands in a Pathfinding report: the roles, the stories, the site map, the flows, the wireframes, the prototype. The client owns it.

Almost all of them get built. Budget decides when rather than whether, and the client is free to take the report to another company or use it to raise the money in the first place, but most of the time it comes back to Animikii and we build the platform.

Which changes what the work has to be. Design documentation usually goes to a team you can talk to, in a building you can walk into. This has to stand on its own, be legible to developers I am not working alongside, possibly years later, and be persuasive to someone deciding whether to fund it at all.

After the report

Pathfinding itself ends at the report. The build is a separate engagement, and I am usually on it: the design work as the archive gets built, and presenting it to the client.

More on Pathfinding