Skip to main content

Backlog

25

Under consideration

Feedback

Daily text: get to the point

What we heard: Greetings and gratitude make the daily text read like spam, especially next to wordy campaign texts. "Thanks for being part of this little community" gave one tester "the ick." Greetings repeat phrases and refer to the bot by name. It is unclear whether a person or an AI is talking. Recommendation: Open with the poll. Allow at most one short line before it, with no self-reference and no thanks. Where warmth is wanted, center the reader or the Staff team, not the bot.

An Anonymous User
Feedback

Ask people to share right after their first poll

What we heard: A tester looked for a way to share with co-workers right after his first poll. The sign-up note on poll pages confuses people who already joined. Short result snippets are what people would talk about. Remote workers share by call or chat, not at a water cooler. Recommendation: After the first vote, send one forwardable line with the link. Turn the poll-page sign-up note into a "bring a co-worker" link. Make each result a snippet that can be forwarded.

An Anonymous User
Feedback

Explain who can see what

What we heard: People asked "Is it anonymous? Is there any verification?" before joining, and were unsure whether results go only to their company or are published to everyone. Named fears: who holds my contact info, co-workers identifying me, employer retaliation, breaching an employment contract. Recommendation: Add a short "who can see what" block to How it works and repeat it in one onboarding text: what Staff stores, what co-workers see, what the public sees, and the 3-employee threshold. Use "confidential," not "anonymous."

An Anonymous User
Feedback

Say what is in it for the worker

What we heard: "To what end?" and "How does it actually benefit me?" came up on every first-look call. The list of who benefits (investors, journalists) read as a threat: "I don't want to give my information to them." At first glance Staff reads as a fun co-worker comparison, not a gauge of American workers. Recommendation: Lead the homepage with the worker's payoff: see what your co-workers and other companies really think. Move investors and journalists out of the opening pitch, or reframe them as people who read the published results.

An Anonymous User
Feedback

Poll page polish: label comments, hide empty sections, add company logos

What we heard: The comment under a poll is unlabeled and reads as a write-in answer. Related and Latest sections show when empty. Company profiles have no logo. Recommendation: Label the comment and add a small anonymous avatar. Hide Related and Latest until they have content. Add logos to company profiles.

An Anonymous User
Feedback

Put How it works, FAQ and Join in plain sight

What we heard: How Staff Works and the FAQ are only reachable through the Join now button. One tester asked around before finding the number to text. The page "goes on for a while" without hierarchy. Recommendation: Put How it works, FAQ and About in the top navigation. Make Join a plain call to action with the number visible. Add section headings to the long page.

An Anonymous User
Feedback

An unknown number feels like spam

What we heard: One tester renamed the contact "Staff" because an unknown number felt like spam or a money ask. Others would not answer an unsolicited text and would check the website first. Recommendation: Send a contact card during onboarding so the thread is named Staff. Keep invitations pointing to the website, not a cold text.

An Anonymous User
Feedback

First reply to JOIN is slow and messages arrive out of order

What we heard: About a 1-minute delay on the first reply made a tester wonder "Is it broken?" Another got onboarding messages out of order. Question and result order differs between Android and iPhone. Recommendation: Send an instant one-line acknowledgment to JOIN. Space picture and text messages so they cannot overtake each other, and test on both Android and iPhone.

An Anonymous User
Feedback

Make the bot and the website feel like one product

What we heard: The site is polished and journalistic; the texts are casual from the first line. Lou appears in texts but barely on the site, "a little bit of a surprise." Cartoons feel "discordant" with the site's design. Recommendation: Introduce Lou on the site next to the join prompt, so the first text is expected. That is cheaper than rewriting the bot to match the site.

An Anonymous User
Feedback

Write questions that work at a 10-person company

What we heard: Questions feel written for 10,000-person companies. At a small, transparent company, co-worker results would not surprise anyone. Recommendation: Check each poll against a 10-person team before it ships. For small companies, lead with how they compare to other companies, since that is where the surprise is.

An Anonymous User

Next up

Committed and queued

No Next up issues

In Progress

5

Actively being built

Feedback

Earn trust before asking for work email, age and gender

What we heard: Testers balked at birth year ("Do I really need to answer that? Can I lie?") and said they would not have given a work email or age this fast without knowing the person who invited them. A gender follow-up felt loaded. One tester has answered an anonymous app untruthfully before. Recommendation: Ship the stripped-down onboarding: first poll before any profile question, then ask one detail at a time with the reason attached. When email is asked, promise in the bot's own words that it is deleted after verification.

An Anonymous User
Feedback

Make clear which poll each result and cartoon belongs to

What we heard: It is unclear when results and cartoons arrive and which poll they refer to. One tester prefers yesterday's result first, then today's poll. "Tap to load preview" links feel less clickable than results shown in the thread. Recommendation: Fix the daily order: yesterday's result, today's poll, acknowledgment, then cartoon. Restate the question in every result. Send the instant one-line result on vote.

An Anonymous User
Feedback

Cartoons look AI-made

What we heard: "Cute but very AI." AI-image fatigue. One tester suggested commissioning an illustrator for 15 to 20 images to remix. Four other testers like the cartoons and say they make Staff feel real. Recommendation: Ship the approved style, then show it to the three testers who objected before spending on an illustrator.

An Anonymous User
Feedback

Let people suggest and ask their own company's questions

What we heard: Testers want to suggest questions for their own company, ask co-workers directly, poll by team or subsidiary, and earn a say in what gets asked by answering consistently. One could not tell whether questions are written by Staff or crowdsourced. Recommendation: Run the team-question pilot and report back here. In the meantime, accept suggestions by text and say on the site that Staff writes the questions.

An Anonymous User
Feedback

Show people their feedback was heard

What we heard: A tester has given feedback but has no idea where it is in the consideration cycle, or whether it was noted. Recommendation: This board is the fix. Give every post a status and change it when something ships.

An Anonymous User

Done

Recently shipped

No Done issues