Blank Canvas

Most design projects start with some uncertainty. This one started with almost none of the answers.

I was working on Virtual Studios, an AI-and-cloud content creation platform. The goal was clear and the deadline was fixed, but the workflows, the feature set, even how people would actually use the thing — none of that existed yet. We weren't solving a familiar problem. We were figuring out the domain and building the product at the same time.

Ask the people who already know

It's easy to assume a designer needs to walk in with answers. We didn't have them — but the stakeholders did. Instead of treating early discovery as a box to check before "real" design started, we used it to actually learn from the people who understood the problem better than we did. The faster we asked, the faster things started making sense.

Get comfortable being wrong, early

Some of our early assumptions were wrong, and that was fine — better to find out in week two than week ten. We told stakeholders upfront that some decisions would shift as we learned more. Nobody was trying to be right on the first guess. The point was to learn fast enough to adjust before it got expensive.

Decide what not to build

Feature requests piled up fast, the way they always do. We started a simple parking lot — a place to put good ideas that weren't critical for launch — so the team could stay focused on shipping a working version instead of chasing every idea that came up in a meeting. Half the job, sometimes, is saying no to things that are genuinely good ideas.

Bring engineering in from day one

Developers sat in on discovery, on workflow reviews, on prioritization calls — not just the handoff. That meant we caught feasibility problems early instead of redesigning around them later. The best decisions came out of design and engineering actually working the problem together, not passing a file back and forth.

Clarity comes before the wireframes

Looking back, the most useful work happened before anyone opened Figma. We needed to agree on the goal, the scope, and what mattered most — in that order. Once that was settled, the actual screens came together fast.

A blank canvas isn't really empty. It's just a project where the clarity hasn't shown up yet — and sometimes the designer's job isn't to hand over a solution. It's to help everyone agree on what the problem actually is.

The honest version of this: none of it was about frameworks or workshops. It was about not having a roadmap, having a deadline anyway, and making progress by asking questions, getting the right people in the room early, and being willing to be wrong in front of them.