In Part 2, I shared the stack that made the Playground possible. Eight tools, four days, zero lines of code.
This post is about what came next.
Playground vs. prototypes
A quick distinction before we go further
Two things in this series share a stage. They aren’t the same thing.
- The Playground is the testing environment I built in four days. It’s the venue.
- The prototypes are the eight new app designs we tested inside it. They’re the show.
Building the Playground in four days was incredible. But not all AI work is that simple. Designing the prototypes that lived inside it took a month. Both are true.
This post is about the slower story, the one that doesn’t make the headline.
The partner
I wasn’t designing alone
The dream scenario for a project like this is dedicated UX research, interface strategy, accessibility planning, and full visual design support across the product lifecycle. That wasn’t the budget I had.
What I did have was Lila Hinds.
Lila joined as a paid contractor. A digital media specialist, designer, and creative storyteller, with experience spanning UI/UX, branding, social media, and community-focused marketing across nonprofit, tech, and service industries. Her work is recognized for strong visual identity, clear communication, and turning ideas into meaningful online experiences.
In other words: exactly the kind of designer this project needed.
The split
How the work divided
Lila took the landing pages and the visual foundations. The pieces that established the language of the platform, the polish a user sees first, the visual ground everything else stood on.
From there, I worked with AI-assisted tools to extend and prototype the follow-through experiences connected to her foundations. Workflows. User journeys. Layouts. Implementation logic.
The hand-off wasn’t clean. It wasn’t supposed to be.
I would share lo-fi sketches. Lila would turn them into UX journeys.
Sometimes that meant translating rough sketches into something polished. Sometimes it meant pushing back on my flows and making them sharper. Sometimes it meant catching experience problems I’d walked right past.
And sometimes, when I was feeling ambitious, I’d skip the sketch entirely. I’d find an established pattern online, a standard login flow, a familiar navigation structure, and share it with Lila as a starting point. Her job then wasn’t to invent. It was to take a generic pattern and make it feel like the Playground.
It was a real collaboration. Not a hand-off relay, where one person finishes and the next picks up. A loop. Sketch, interpret, push back, refine. Repeat.
The constraint
What designing under real constraints actually looks like
Necessity breeds innovation, but it also breeds humility.
I have always believed I have an eye for polish, even if I can’t always produce that level of polish myself. That distinction mattered. It meant I could direct AI tools toward layouts and structures that felt right, but I couldn’t always get there alone. And it meant Lila’s eye, on the parts she owned, made the rest of the platform possible.
What surprised me wasn’t how much AI could help me prototype. It was how much I still needed a designer in the loop. Not as a polish layer at the end. As a thinking partner throughout.
AI shortened the distance between my product thinking and a working prototype. Lila made sure what came out the other side was something a user would actually want to use.
The takeaway
Access, not expertise
Here’s the line I keep coming back to.
AI changed my access. It didn’t change my expertise.
Refining the eight prototypes took a month. A month of pulling in user feedback and performance insights from the MVP, documenting every design decision in Asana, and polishing the work until it could hold up to the 95% adoption rate we’d already earned. AI let me move faster between rough idea and working prototype. Lila made sure the work was something a user would actually want to use. Neither of us was going to shortcut the part that actually mattered.
It let me explore workflows I couldn’t have built manually. It let me participate more confidently in the design process under tight constraints.
But it didn’t replace what Lila brought. It didn’t replace UX research, accessibility awareness, visual hierarchy, or the human judgment of a designer who has trained her eye to see what most people miss.
The story of designing inside the Playground isn’t “AI replaced our designer.” It’s “AI made it possible for one designer and one PM to do the work of a much bigger team, over a month of feedback, refinement, and human judgment, not a long weekend.”
That’s a different story. And it’s the one that’s actually true.
What comes next
What comes next
The prototypes were built. The Playground was live. The platform was ready to put in front of volunteers.
What they did with it, and what it taught us about the people we’d been designing for all along, is the next chapter of the story.