The setting
's is writing assistance software for creating and revising text. It comes in versions for businesses and for education.
Tomorrow’s agent release turns a misunderstood permission into an irreversible disclosure.
Uninterrupted activation protects adoption, while document-by-document approval protects deliberate control over text sharing.
Who you’d be doing this for
“I selected two sentences, then someone asked whether the rest of the document went too. I honestly didn’t know.”
Johanna Gordon · Client delivery manager · a character in this brief
Prepares client updates containing internal discussion and uses the writing agent to revise selected passages.
What is at stake
A writing agent reaches 18,000 employees tomorrow, but testers misunderstand which text it receives. You must weigh uninterrupted activation against deliberate permission when shared text cannot be recalled.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- uninterrupted activation vs deliberate authorization
- real writing behavior vs bounded sample documents
- release timing vs confidence in comprehension
- simple wording vs accurate processing scope
Why Superhuman
Superhuman Go brings writing assistance into existing applications, where permission language determines what employees believe leaves their documents.
Written with these in mind
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)
- Your design and strategy will reach millions of people daily and make Superhuman’s value and first impression clear and motivating, from the moment they discover us through an SEO page or product page to signing up and trying our products for the first time.
- Senior Product Designer, Cross Activation (opens in a new tab)
- Staff Product Designer (opens in a new tab)
- We often start in code, refine in Figma, and ship frontend changes back into the codebase.
- Words are the product here, so we want someone who also thinks about how a sentence works, what makes writing sound like a person, and how tone shifts depending on who you're talking to, not just the interface around the words.
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.
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.
Testing before launch showed people mixing up file access, link scope, and outside invitations.
You have to make each sharing action clear without slowing the work down.
AI Teammates are surfacing work from projects users can no longer open.
You must weigh retrieval speed and cross-project usefulness against a permission boundary that cannot be casually reversed.
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.
Cross-surface tasks take a median of 7.4 navigation actions, and support data ties the confusion to delayed production changes.
You have to decide how developers move between workflows, evaluations, connections and deployed agents before deep links and permissions migrate and set that path.
Admins stall at permission validation and destination selection, and many misread what happens when a connection is committed.
You have to settle the interaction model now, because changing it after rollout is costly.
In audit samples, interviewers saw context that some customers do not permit, and the migration runs one way.
You have to keep scorecards structured and auditable while narrowing what interviewers see.
