3 ms·
As a general advice: Always communicate in terms of what the recipient cares about. If your recipient is a business person, you should communicate in business t
by jononor 6y ago
As a general advice: Always communicate in terms of what the recipient cares about. If your recipient is a business person, you should communicate in business terms. No-one really cares what things you are trying out, issues you have et.c. - only the consequences for them / the business. It may seem like this is just two sides of the same coin (and it is) - but which side you approach it from makes a massive differences in the communication.
A startup cares about business traction, functionality that helps existing or getting new customers. So a status update should be on how one is now closer to (or unexpectedly further away from) that.
Note also that in a startup vision of the product, usage scenarios, user groups and business model often tend to evolve over time. You must make sure that you are up to date with the latest learnings, and that your development plans are inline with these.
If you don't make sure to do this, your work may be perceived as (and/or be) irrelevant to the company success.
- jdmichal 6y agoThis is it right here. You can either expect all the people hearing your stuff to learn enough about engineering to understand your engineering statuses. Or you can learn enough about what the business values in your work to rephrase it that way instead. And hopefully you already understand the latter!