During stand up for a very small team on a small startup, what should I be informing them to provide value?
I know the typical, "what you did, what you're going to do, blockers"; but, I feel like thats kind of basic. On the flip side, I feel if I get too much involved in what I did and perhaps implementation details, they might not necessarily understand or care.
For context, our team is very small, and our CEO/CTO are the other devs so I feel like I need to tell them more, but not sure where to draw the line.
![Mid-Level Software Engineer [E4] at Meta company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fmeta.jpeg%3Falt%3Dmedia%26token%3Da7a5bcc0-e178-4b5b-b71e-09bf6c6aefae&w=48&q=75){kind=small}
Discussion
(2 comments)- 6 months agoTech Lead/Manager at Meta, Pinterest, Kosei
I like your approach to deliver valuable updates in standup, by asking the question "what does my team actually care about?"
The way I'd do this is to look at the top 2-3 priorities for your team (I guess, in your case, the whole company), and figure out how your work ties to that. Then in your standup update, make the connection clear. At the CXO level, they probably care about things like timeline, and anything you're doing that could speed up or slow down the shipping date.
Related content about standups in Taro:
1 Like - 6 months agoEngineering Manager at Blend
For my team I implemented standup 2.0
- We use geekbot to cover all the standard questions (yesterday, today, blockers)
- We use standup meeting to talk about the juicy stuff (blockers, distractions, shipping on time) <-- Like Rahul said, generally this is what leadership cares about.
1 Like
