Weekly Update Template v1
One of the things that had been missing -- and I feel I could have exerted much more direction and leadership -- was how we are doing updates to bring people along and raise risks.
The thing with these updates is that they need to work across different channels (zoom calls, slacks, ICs, Execs) and this is tough to do, but very important.
So I'm going to start researching how to do this, but start by solving my own problem and see where this takes me.
Version 1 looks like this:
What/Why
This may be repetitive, but I think this is important. If there's an edit in what we are doing, this could be a way to highlight it.
What got done? What actually happened?
What was the impact? Why does this matter? Can we measure it?
What is not moving along to plan?
Next Up should list what's next up with Target Dates so we get a feel of the high level plan.
This week's customer insight: this is important because PM needs to talk to customers. It's a soft way to say, "Hey, we need to fix this, HOP or BD or someone, this is a sign of a broken process".
XFNs - how are we working across the team so that they are informed, provide links to working spaces or short product notes.
Part of me is frustrated that I didn't take the initiative on this; but it's hard joining a brand new company to do this, but this is the way to start to share, just share information, share what I've been working on, get onto people's radars.
One way that I see now, just by sitting here and thinking, is to consider comms as "sharing" and "teaching."