One Community Together: Strengthening British Community-Building Organisation
How a non-profit organisation supporting community hired a UI/UX Designer and a WordPress Engineer.
Challenge
One Community Together is a London non-profit supporting mothers through English and digital skills classes, community projects and wellbeing programmes, delivered with local partners and funded project by project. Its website has to do three incompatible jobs on one set of pages. A mother considering a class needs to know what it is, where it is and whether she will be welcome in the room. A volunteer needs to understand what giving time actually involves before they offer it. A funder deciding whether to back the next round needs to see an organisation with a record, and that judgement gets made in about fifteen seconds by someone who will never tell you they made it. Small organisations usually solve this by serving the first audience properly and leaving the other two to a contact form.
The organisation is run by one founder, who is not technical, and every hour spent on a website is an hour not spent on the work the website exists to describe. So two requests went in with timing attached: a UI/UX designer with six years and more of production design systems and the full span from research through to interaction detail in Figma, and a WordPress engineer with nine years of production WordPress behind them, writing themes and plugins rather than assembling them in a page builder, with REST API integration where pages needed to connect to something, across PHP, WordPress Core, Gutenberg, React and MySQL.
Pairing them mattered more here than it usually does. With a single non-technical founder there is nobody in the middle to turn a design into a brief or to catch what falls between the two, so the designer and the engineer had to handle that themselves. Screening followed from it: people who had built for small organisations where credibility does the converting rather than features, who could route three audiences through one site without inventing three navigations, and who were comfortable with a client who had very little time to review anything. Both engagements were confirmed 10 hours after the request opened.
Outcome
Timing required the design and build to be run together with neither person needing managing. That was the whole decision: one founder, no technical staff, no capacity to coordinate, and two people who had to arrive able to work as a pair from the first day.
- Two requests, both filled and engaged within 10 hours.
- Design and implementation covering a site serving mothers, volunteers and funders at the same time.
- Delivered for a single non-technical founder with no staff and no in-house capability.
- Engagement from the first day to a design concept, and a live site.
A Strategic, Multi-Phase Hiring Approach
Phase: Request
Two requests at once - a UI/UX designer on Figma and design systems, and a WordPress engineer on PHP, WordPress Core, Gutenberg and MySQL, with timing to deliver.
Phase: Matching
Candidates were weighted towards work for small organisations where credibility is the conversion, towards sites routing several audiences without fragmenting the navigation, and towards people able to work with a client who has little time to review.
Phase: Interviews
The founder interviewed 6 candidates himself and chose 2, both agreed 10 hours after the request opened.
Phase: Engagement
Part-time workloads and hour caps were agreed for each engagement beforehand, tracked daily in the internal tracker, and monthly reporting.
Phase: Support
Engagement included design concepts and site releases throughout one month, with workload changes requested and approved.
