top | item 7151791

Asana’s Justin Rosenstein on the One Quality Every Startup Needs to Survive

42 points| zt | 12 years ago |firstround.com | reply

15 comments

order
[+] johnrob|12 years ago|reply
In my experience, lack of clarity is caused by the executive team not making their true goals known to the whole company. A classic example is prioritizing seemingly arbitrary products/features in hope of pleasing a future partner or acquirer - employees won't automatically know why these obscure projects suddenly became important.
[+] samstave|12 years ago|reply
If the startup needs clarity to survive, then the exec level must have transparency to reach clarity.

If you do not have transparency; then clarity (about your true goals) is impossible, because execs with lack-of-transparency typically have other (more selfish/shady) goals that they are really requiring people to support through their work.

Typically, their (the execs) actual greed.

I have oft stated in the past that another positive outcome from transparency is also accountability.

[+] staunch|12 years ago|reply
Everything seems very clear to a founder because the founder defines what clarity means! Clarity comes from authority and agency. I bet that engineer is back in the dumps within a day or week.
[+] winslow|12 years ago|reply
I agree. Happened to me today in a matter of hours. Something I'd been working on for the past couple days (mundane task) just got "nuked" with a new requirement list which will now wipe our data in the database that I just finished connecting to our code. This big company is so inefficient it's maddening, I don't believe my group will ever release a product. /rant (sorry)
[+] callahad|12 years ago|reply
To un-bury the lede, his answer is "clarity."
[+] zaidf|12 years ago|reply
One of the top complaints from employees at startups I've worked at has been the constant shuffling of priorities without clear justification. It manifests in this way typically: founder tells company on a Monday that the priority is x; then in middle of the week says priority is y while being oblivious to the fact that y directly contradicts x. This leads to the barrage of water cooler gossip wondering if the founder knows what the heck he is doing.

The sad thing is that usually founders have good reasons to constantly reassess priorities especially in early stages. But to change priorities without a clear transition about the why turns your passionate star employees into confused bots wondering why they are working for you.

[+] doorty|12 years ago|reply
I can relate to this as a developer. At my agency, the technical team is often brought in later-on in designing a solution, and I find myself not having any base understanding of the project--like why and for who is this being developed. As a result, it's hard to have motivation to work on a project when you lack the why's of what you're doing.
[+] jaiball|12 years ago|reply
A problem well defined is a problem half-solved - a great fortune cookie quote I recently came across and has been resonating with me alot lately. Its tough to move forward without having a clear vision of what needs to be done.