3 ms·
Transparency is great, and I think the main balance that might be missing in this context is how much frequency/latency there is between events that are taking
by anomaloustho 4y ago
Transparency is great, and I think the main balance that might be missing in this context is how much frequency/latency there is between events that are taking place. I see it more like a stock ticker. There are ups and downs, some big swings that happen at a micro scale, and then overall trends.
It’s good to identify how much frequency your team can handle and where to dial that in.
E.g. Monday: really hot lead, Monday afternoon: just got off call, lead upset about missing feature - not sure if deal will happen, Tuesday: contract sent. Wednesday: Lots of red lines, not sure if we can do this. Thursday: Deal signed. — This is very high frequency reporting with lots of ups and downs. It can be hard for a team to even focus with this amount of thrashing.
Another example: Monday: Prospective client, Next Monday: Contract won/lost, and these are the reasons.
- quickthrower2 4y agoThis is about knowing your audience. Sales manager would want all this info. Engineer probably doesn’t. Same way sales person doesn’t need “looks like bug is fixed” “failed a CI test” “getting help from platform team” etc…. Just “the SSO bug you raised last week is now fixed”