Tools

Tools I’ve designed and built

A few problems I wanted to try solving

In my work, I sometimes come across things that are harder than they need to be. It might be understanding what a role really requires, finding patterns across interviews or making sense of accessibility issues on a website.

Some of those problems have made me curious enough to start building tools of my own.

I use AI to help build them, but try to start with the same questions I ask in my design work: What is someone trying to do? Where does it get difficult? And what might make it easier?

The tools are free to try. Some require a free account after a number of uses, and a few are still evolving. I’d love to hear what works and what could be better.

Recruitment and skills

From a clearer role to a better conversation

A job advert doesn’t always explain what matters most in a role. And a CV doesn’t always tell the whole story of someone’s experience.

These tools help make requirements clearer, explore how experience relates to them and identify useful questions for a conversation.

  1. Clarify the needThe recruiter makes the ad clear and fair, and gets an interview guide.
  2. MatchThe job seeker matches their CV to the ad and sees matches and gaps.
  3. ShareThe job seeker can send the match as a link: evidence for each need, never the CV.
For job seekersAn honest first draft for your cover letter, a checklist of matches and gaps, likely interview questions with examples from your CV, and a link you can share with the recruiter if you want to.
For recruiters and hiring managersWhat the role really needs, wording that may put good candidates off, and the same interview questions for every candidate. It never assesses candidates: people decide.

Research and insights

From interviews to something your team can use

Working through large amounts of qualitative material can be difficult without losing the nuances.

  1. ObserveEvidence-near observations from each interview, with names removed.
  2. SynthesiseFindings, key insights with evidence strength, and opportunity areas.
  3. DecideWhat it means for your decisions, what is still unknown, and a knowledge base you can ask.
After interviewsUnderstand behaviour, situations and friction: what people do and why, and why it matters for what you develop.
After concept testsEach concept analysed on its own, with an evidence class from A to D, so a positive reaction is never mistaken for validation.

Accessibility · WCAG 2.0, 2.1 and 2.2

Find issues, improve the code and check again

Accessibility needs both technical checks and human judgement. I’ve built two tools designed to work together.

  1. CheckThe Checker tests your site and reports what to fix first.
  2. FixThe Fixer repairs the safe issues in your code and lists the rest as tasks.
  3. VerifyCheck again: the report confirms which fixes hold.
The Checker on its ownFor designers, product owners and anyone who needs to know where a website stands: a report with what to fix first, and a plan for the tests that need a person.
The Checker and the Fixer togetherFor teams who want the issues fixed: the safe ones are fixed in the code, the rest become tasks for an AI coding assistant, and the next check confirms the result.

More tools are on the way.