Designing for the Next Generation: A Slack Product Vision

Case study in the series behind How I Whiteboard Product Interviews Live. Method: The Live Whiteboard Method.

Want the product, not the board? The companion post A Safe Social Chatspace for the Next Generation goes inside the actual product: minor safety, privacy, and UX.

The prompt came from a product studio that was hiring, and it was a take-home rather than a live board: design a new product or feature for Slack's "next generation of users." The setup was that those users feel Slack has gone "too enterprise" and lost "the magic." It is a deceptively open brief. The temptation is to jump straight to a feature and a flashy mock. The actual work was upstream of all that.

Here is how I approached it.

I translated the prompt before I designed anything

The first thing on the board was not an idea. It was the prompt itself, taken apart. I pulled the load-bearing phrases out of the brief and pinned them up word for word: "the next generation of users," "too enterprise," "missing the magic," "the latest tech."

Then I sorted them into the decomposition I reach for every time: Audience, Technology, Problem-to-solve. Audience was "the next generation of users," which I refused to leave vague. Technology was "the latest tech," an invitation, not a constraint. Problem was the pair of phrases doing the emotional work: "too enterprise" and "bring the magic back."

Only after that did I write the one-line vision the phrases added up to, and immediately wrote the question most take-homes skip: how would we measure this? A vision you cannot measure is a mood board. Naming the measurement question up front signals that you intend to build something real, not just something pretty.

I grounded "next generation" in real research, not vibes

"Next generation of users" is the kind of phrase that lets people design for an imaginary teenager who behaves exactly how the designer wishes. I would not do that. So the next section of the board was a real research snapshot on Gen Z and Gen Alpha: who they actually are, how they actually communicate, and what they actually value. Short-form, visual, voice and reaction over long threads. Identity and belonging over productivity. Presence and play over inbox-zero.

That snapshot did two things. It kept the design honest, and it surfaced the uncomfortable fact that everyone else was designing around.

The compliance reality check I refused to skip

"Next generation" includes minors. The moment you say that out loud, the whole problem changes shape.

So I put a child-safety and COPPA reality check directly on the board, as its own section, not a footnote at the bottom. If the audience includes kids, then data collection, parental consent, default privacy, and moderation are not features you add later. They are constraints that bound the entire design space from the first sticky. A "social chatspace for the next generation" that ignores this is not a bold vision. It is a liability.

This was the strongest move in the whole take-home, and it was the least glamorous one. Most submissions to a prompt like this will hand back a fun teen-Slack concept and never mention that designing for minors is a regulated act. Naming it is what separates a product person from a feature person.

The vision, and four principles to hold it together

With the audience grounded and the constraints named, the vision got concrete: younger users making connections in social chatspaces, a place that feels like belonging rather than work.

To keep that from sprawling, I anchored it to four design principles, each one a filter every feature had to pass:

• Safe, because the audience includes minors and safety is the precondition for everything else.
• Simple, because "too enterprise" is really a complaint about cognitive load.
• Familiar, because the magic lives in patterns this generation already loves elsewhere.
• Engaging, because presence and play are the point, not a metric to bolt on.

Principles like these are not decoration. They are how you say no later without re-litigating the vision every time.

I sequenced it like a deck, not a wish list

The last move was to give the vision a shape someone could act on: Outcome, then Focus Areas, then Features, then Next Steps. The outcome at the top, the two or three focus areas that serve it, the features under each one, and the next steps to validate before committing. That spine is what turns a vision into a plan, and it reads top to bottom as an argument: here is what we want to be true, here is where we will work to make it true, here is what we would build, here is how we would check.

What the board was really showing

There is no proprietary framework here. What the take-home demonstrates is a way of thinking that someone else can follow:

• Translate the prompt into its real parts before designing anything.
• Ground a fuzzy audience in actual research instead of a convenient fantasy.
• Name the constraint everyone else is avoiding, even when it is the boring one.
• Hold the vision together with principles that let you say no later.
• Sequence it into outcome, focus areas, features, and next steps.

Designing for the next generation means designing for kids, and that is a product constraint, not a footnote. The board that says so out loud is the one I would trust with the real thing.

If you want to see this live, bring me a real product problem and watch me whiteboard it end to end: that is the Watch Me Think offer. To practice the method yourself, the Whiteboard Prompt Translator scaffolds the six frames from any prompt.