Observation created over 4 years agohttps://lessonly.slack.com/archives/CU371H1RQ/p1601401557018300
That post is so simple, but here is what it does:
- Reminds everyone of the context
- Asks everyone who might be impacted, therefore showing off a mission-control style information sharing
- Gives clear reason why this group should care
- Hints at next step (if it had a timeline on when the switch was going to be made, it'd been perfect IMO)
Observation created over 5 years agoHere is what I love about this...
- Initiative:
- This was not something that I anticipated Rick jumping in on. However, he saw it, knew he could make it better, and executed brilliantly.
- Understand the audience:
- Hippo has traditionally needed things to be crystal clear when asking them to do a thing or answer a question. So, he took the time to write out clear instructions for them, which gives us the best chance of this being a successful encounter.
Well done sir!
Observation created over 5 years ago❤️ the fact that it was informative
❤️ the fact that it gave clear examples of what should be expected (high enough quality to probably just put into a knowledge base)
❤️❤️❤️❤️❤️ the fact that it gave guidance to the requester of what to do next... and what to do next includes a ZD ticketThe hope is that a few good responses like this will get folks to use the ticketing process without them feeling bad for asking.
Well done Rick!
Observation created over 5 years agohttps://app.clubhouse.io/lessonly/epic/27348#activity-32580
This is how acceptance criteria should be written.
This level of detail should be at the story level to ensure clarity.
However, I'd put this level of detail in the epic in scenarios where there is less design, or complicated logic, or a delivery team that doesn't find joy in pushing the boundaries on the details.
Observation created over 5 years agoHiring is hard.
It is time-consuming, it is nerve-wracking, and it is easy to get overwhelmed with the work of shepherding candidates through the process.
However, it is the single most important thing we can do to continue our journey to be the greatest product team so that we can help fuel the greatest organization which is here to push forward one of the greatest missions of our time :-) (couldn't help myself :-) )
When someone comes in and finds a way to improve any part of it, I'm thrilled.
In this case, Rick posted an update from the week of what was done, and where his head is at.
https://app.clubhouse.io/lessonly/story/29768/hire-product-quality-engineer#activity-30491
That is HUGE... and here's why... clarity and transparency are better work.
We love transparency here. So, posting an update like this directly impacts folks' ability to follow along and be a part of the process. Also, anyone who is interested never has to ask "where are we with that", because it is in the right place, it is concise, and it is clear.
:spidey-dance:
Great job man... keep it up!