On November 9, 2010, someone building a startup called Rah made a curious request. Did anyone have their startup interview on November 15 or 16? Rah’s team had an interview on November 18 and wanted help from people going first. They offered critiques, beta testing, even T-shirts in return. A reader naturally wondered what an experienced founder hoped to learn from other applicants. The answer was more interesting than reconnaissance: the team wanted people to use its feedback product during the interview itself.
- Rah began with feedback for meetings.
- By January 2011, its stated focus was automated peer review for startups.
- Its team argued for a more transparent workplace meritocracy.
- The surviving LinkedIn page says the business ended around early 2011.
There was a snag. The original request had not explained that it was a product test. Another reader pointed out the ambiguity; the author accepted the criticism and asked how to correct the post. A company making feedback software had just received useful feedback on its own pitch. It is a pleasingly economical origin scene: no garage, no thunderbolt, just a misunderstood question becoming a better one.
A meeting was the first unit of measurement
At that point, the team described Rah as “a feedback product for use in meetings.” That sentence gives the early product a specific setting. Meetings bring people together to explain, persuade, decide and sometimes perform elaborate impressions of making progress. Rah proposed putting feedback inside that setting. An interview offered a particularly concentrated version: a short conversation, high stakes and people trying to understand how they had come across.
The intended users were therefore people taking part in meetings. One respondent, who said they worked at CBS, expressed interest in sharing the idea amid a run of agile meetings. That exchange illustrates the use case rather than a customer contract. A person recognizing a problem is the beginning of commercial discovery; it is not yet a sale.
In that setting, the functional alternative is familiar: leave the room, ask someone how it went and hope their answer contains something more useful than “fine.” Rah’s early description offered a product around that moment. The interesting competitive question was whether a deliberate feedback process could improve what an ordinary debrief already did. The room supplied the occasion. The software still had to earn its place in it.
The office had supplied the grievance
The team introduction named two people, Mike and Nicki. It described Mike as a previous Y Combinator participant with an exit, and Nicki as a Stanford double major with an eye for design. Professional histories identify P. Michael Ossareh as a Rah co-founder. Those backgrounds help explain the combination of software and workplace concerns in the project without making its pedigree a substitute for its product.
Nicki supplied a first-person explanation in a November discussion about working at large companies. A productive group inside T-Mobile, Nicki wrote, had been held back by the infrastructure around it. That frustration prompted a departure to start rahfeedback.com. The complaint was precise: a capable team could accomplish things internally while the surrounding organization impeded its work.
Another team comment expressed the ambition as “a far more transparent meritocracy.” It is a compact phrase with a large bill attached. Transparency concerns what people can see. Meritocracy concerns how they are judged. Put the two together and a feedback tool starts touching recognition, advancement and authority. This is the editorial implication of Rah’s stated ambition, rather than a claim about features it shipped: better information was meant to matter inside an organization.
“a far more transparent meritocracy”
Rah team member dayjah, November 2010
By January, the question had become a career
On January 5, 2011, Rah’s team asked Hacker News readers what they had learned from their most recent performance review. The post linked to a beta and described the work as a startup-friendly automated peer-review system. It invited people to explain what worked, what did not, what they learned and what they wished they had known. It also asked for company size.
Compare that description with the November one. A meeting is an event. Peer review evaluates someone through other people’s experience of working with them. The subject had grown from a conversation to a relationship. The public wording shows a change of emphasis; it should not be turned into an invented boardroom scene in which the founders dramatically abandon their first idea.
The January request also sharpened the audience. Startups were now named explicitly. Asking about company size suggested that context mattered to the team’s research. Five colleagues and five hundred colleagues do not experience the same review process. Rah was asking about the surrounding organization as well as the review itself.
Its most useful question was the first one: what did you learn? An evaluation can produce a rating without producing an insight. A review can satisfy a deadline without helping anyone decide what to do next. As an analytical reading of the post, Rah’s wording made learning a possible test of usefulness. That is a more demanding standard than the mere completion of a form.
Recognition came with a pay-raise objection
Rah’s public blog submissions ranged across bureaucracy, company culture, professional development and employee recognition. Titles discussed Justin.tv, Photojojo and a Get Satisfaction co-founder. These were subjects of the team’s publishing, which placed Rah’s attention in the world of organizational habits and startup work.
A December post about public recognition drew a blunt objection: perhaps raises were the more important ingredient in engagement. Nicki’s response acknowledged money as a key factor and discussed the relationship between basic needs and esteem. It is a useful exchange because it puts a boundary around the appeal of praise. Recognition has to live alongside the material terms of a job.
For anyone borrowing from Rah’s premise, that boundary matters. Feedback might make a contribution more visible. It cannot by itself improve pay, give someone decision-making power or make a manager respond. A proposed feedback process needs a clear connection to action. Otherwise, the office simply acquires another place to record its disappointments.
The company ended; the profile stayed
The surviving LinkedIn page now calls the business DEFUNCT COMPANY. Its description says it stopped existing around early 2011 and complains that LinkedIn will not allow the page to be deleted. The company that objected to organizational friction left behind a small, dry example of administrative persistence. A profile is evidently easier to keep than a business.
Read Rah today as a historical attempt to improve workplace feedback. Its practical lesson is an interpretation of the questions its team asked: begin with an actual occasion, invite criticism of the process and judge the result by what a person can do next. A manager could copy that approach with a short debrief: what helped, what confused you and what should change before the next meeting?
That approach depends on people being able to answer candidly and someone being willing to act. If the answer carries a penalty, or disappears into a drawer, collecting more of it will achieve little. Rah’s brief public history leaves us with a useful standard for any feedback system: after the conversation, the working day ought to become a little easier to understand.