← Superhuman
Complex day at Superhuman

Fix what admins read when a move widens access, before release

Published Nov 5, 2026

You’re the product designer. Your team is in the room.

Run your first brief, free

The setting

makes , a collaborative document application with tables, for teams that start by building a tracker in a doc and end up running a real application.

A folder move changes the audience before its consequences can be taken back.

Keeping document organization available conflicts with preventing disclosure that a confirmation may not make understandable.

Who you’d be doing this for

“I moved the tracker into the department folder, and someone outside the project asked about a row ten minutes later.”

Chioma Boateng · Enterprise Document Administrator · a character in this brief

Reorganizes operational documents for departments whose folder memberships differ.

What is at stake

Eight of 12 administrators misread who gains access after moving a document. You must weigh a usable confirmation against suspending moves whose disclosures cannot be undone.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • informed consent vs enforced prevention
  • specific access claims vs incomplete membership detail
  • routine organization vs irreversible disclosure
  • rapid testing vs representative behavior

Why Superhuman

Connected tables make a document move more consequential than moving a standalone page.

Written with these in mind

Enterprise product designersSystems-minded interaction designersDesigners of high-consequence workflows

Not your kind of problem? 42 more at Superhuman, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Superhuman. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Sr. Growth Designer, Web Acquisition (opens in a new tab)
    • Growth Strategy: Create strategies and design solutions for our websites, landing pages, search surfaces, and other top-of-funnel surfaces that attract and convert new customers, collaborating with marketing teams to understand target audiences, content and positioning, user journeys, and branding.
    • Communicate and collaborate: Work closely with marketing, product, and engineering teams to align designs with business and acquisition goals.
  • Senior Product Designer, Growth (opens in a new tab)
    • The company’s products include Grammarly’s writing assistance, Superhuman Docs’ collaborative workspaces, Mail’s inbox management, and Go, the proactive AI assistant that understands context and delivers help automatically.
  • Senior Product Designer, Docs (opens in a new tab)
    • At our Porto office we have several teams actively working on product-led growth, reworking our mobile app for the AI era, delivering AI powered Tables in Superhuman Docs and integrating Go (our new suite wide AI assistant).
    • Shape the product direction: bring a design perspective to the early product thinking (not just the execution) by contributing to roadmap and strategy discussions.
  • Growth Design Manager, Web & Acquisition (opens in a new tab)
    • Contribute to and expand scalable design patterns, templates, and component systems that allow the team to move fast without sacrificing quality.
    • Collectively represent and advocate for how we raise and hold a high design bar with cross functional partners.
  • Senior Product Designer, Cross Activation (opens in a new tab)
    • Collaborate with designers and product teams across Grammarly, Mail, and Coda to identify cross-product discovery opportunities, foster shared learning, and develop cohesive experiences across the suite.
    • This is a highly collaborative role that calls for strong product intuition, exceptional craft, and a data-informed approach to design.

Reporting read before this brief was written

The pieces closest to the situation in this brief.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Run your first brief, free

Where similar work appears

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these turns on moving faster inside a system others depend on.

The same setting, from another role

Each is set around Superhuman’s Superhuman Docs, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to make complicated, high-stakes systems feel simple to navigate without quietly removing the protections people depend on.