General product check in.
Strategy, notes, testing and hype.
Few more mobile improvements to make, trending assets for what you want on the go, remembering the last wallet, fixing some polish. At this point happy to just close the project and begin anew since it’s feature complete. From a clean slate we can handle the other pieces.
Notifications are getting more polish tickets and extending our view for the user experience everywhere.
To wit, removing all status screens in the app has it’s acc and mocks for the experience. Each flow is considered with the toast versus the action center trigger. Hoping to groom this out monday, because it’s a big ticket (possiby even worth it’s own project IMO). Everywhere users sat with a tab open is an opportunity to finish what you came for, or start another action. Endgame is notifications are for things you actually did here(Discord).
Process & Research & Team
Several groomed issues ended up back out of the pipeline this week, leading to a sluggish end of week for devs. This was supremely frustrating for everyone involved. Status screens instead of confirmation modals, clearly labelling the swappers, and trending assets underneath the mobile trade view. All of these had unrefined issues with meager acc, didn’t get a proper look, and were not “ready for pickup…..” despite being groomed on Monday. Change is needed.
However!! @Neomaking crystallized the issue we’ve been having for so long: not enough pre-grooming.
Product ++ eng is going to do more of the ACC back<>forth iteration before the cycle starts. It’s been a nagging nest of contradictions: both finishing too much work and not having enough groomed work. Too much ambition/vision (on the agent) and no vision (on the app). We agreed to deprioritize but it seems like we’re getting stuck on velocity for velocity’s sake.
So, we’re going to fix this! We can do it and get towards prioritizing for impact. Impact brings momentum and clearer ACC, and working collaboratively means no more tickets stuck in the cycle that shouldn’t be there. sometimes you need to go slow to go fast.
We all want the same thing: to execute at our best level and raise the momentum dial one notch. It seems like some of us put the notch at like 16 and others two notches. Aligning everyone back to grid.
I’ve visualized this process exchange here in a ticket lifecycle:
Data & stat of the week
Dashbaords:
Conversions - Request Access - Mixpanel
Trades - Request Access - Mixpanel
Wallets - Request Access - Mixpanel
Trade Conversions back up above 2.3%!! (this was like 1.9% for a long time)
Spec updates:
Spec Backlog is going to get a refresh thanks to @Tyler_ShapeShift engaging his brain for old ideas of a decade of building. Could they work now? What low hanging fruit did we throw out along the way?
In progress linear
Cycle breakdown
Other feature process:
- add a feature you’d like to see at shapeshift.canny.io and bring your friends for upvotes
- Response KPI :
couple of leaking support issues onto canny.
- specs board
G to the M
