Amazing post David! I'm just wondering how to balance the workload of the UX contributor (let's take your example). This person will be pretty involved in Discovery activities, but it is also required to deliver a lot of artifacts for the rest of the team.
I don't see this happening with Devs or PMs because they can rely on other teammates or even do not need to build something shippable.
- UX people work about 70% of their time doing discovery activities
- UX people use 30% to work with the team doing the delivery
- The result of discovery would already create the necessary assets and contexts
- Devs work as achievers, not coders. They take ownership of crafting based on guidance from PM and UX
Of course context matters, depending on your situation, assets need to be pixel-perfect. Yet, that's rarely necessary, though many teams act as if that's fundamental.
Amazing post David! I'm just wondering how to balance the workload of the UX contributor (let's take your example). This person will be pretty involved in Discovery activities, but it is also required to deliver a lot of artifacts for the rest of the team.
I don't see this happening with Devs or PMs because they can rely on other teammates or even do not need to build something shippable.
Any thoughts on this? Thanks!
I see the following:
- UX people work about 70% of their time doing discovery activities
- UX people use 30% to work with the team doing the delivery
- The result of discovery would already create the necessary assets and contexts
- Devs work as achievers, not coders. They take ownership of crafting based on guidance from PM and UX
Of course context matters, depending on your situation, assets need to be pixel-perfect. Yet, that's rarely necessary, though many teams act as if that's fundamental.