The document discusses how to effectively organize work across multiple teams to deliver projects while applying UX and agile principles. It recommends treating projects as hypotheses and prioritizing discovery work to ensure projects address business goals and customer needs before committing resources. Specific tips include limiting work in progress, using visualization tools, establishing clear stages for discovery, delivery and monitoring, and continuously reviewing processes to apply learnings.

1. Salut !

2. Salut...
I’m Tiago, from Brazil. In France since 2017…
🇧🇷
Biloute 😝

3. Salut !
Wife and cats came along...
😍

4. Salut !
…I was really well received. Even got invites to dinner with friends…
...often on Wednesdays evening…
😝

5. Je rigole. ;)

6. Salut !
I “tu toi” everyone because in Brazil we don’t have “vous”...
...I mean everyone…
😝

7. Ouais 😆

8. How might we leverage
UX and Agile
to deliver great products?

9. Some math for context...

10. 1 company
Clear business goals
246 projects mapped for the year
147 digital projects (features, new stuff)
25 squads

11. 1 company
Clear business goals
245 projects for the year
147 digital projects
25 squads
147 / 25 = 5.8 projects per team

12. 1 company
Clear business goals
245 projects for the year
147 digital projects
25 squads
147 / 25 = 5.8 projects per team
5.8 / 12 = Almost one project per month per team.

14. But…
I have one question

15. 1 company
Clear business goals
245 projects for the year
147 digital projects
25 squads
147 / 25 = 5.8 projects per team
5.8 / 12 = Less than one project
per month per team.
Can 1 team deliver 1 project without help
from another team?

16. Usually… no. And that’s normal.

17. So, let’s update our math...

18. 1 company
Clear business goals
245 projects for the year
147 digital projects
25 squads
147 / 25 = 5.8 projects per team
5.8 / 12 = Almost one project per month per team.

19. 1 company
Clear business goals
245 projects for the year
147 digital projects
25 squads
147 / 25 = 5.8 projects per team
5.8 / 12 = Almost one project per month per team
5.8 (projects) * 4 (hypothetical number of teams needed to deliver 1 project in a given organization) =
23.2 “projects” per team
23.2 projects / 12 months = ~2 projects per team per month

22. What should we discuss
about ?
Delivery deadlines?
Requirements lists?

23. How are we impacting business goals
How about

24. If we get back to our context

25. 1 company
Clear business goals
147 digital projects (features, new stuff)
25 squads

26. 1 company
Clear business goals
147 hypothetical solutions (features, new stuff)
25 squads

27. Every work we do should impact business
goals to either make it progress, either
provide feedback based on customer
satisfaction to improve it.

28. We should as be good to
discover and dump hypothesis
as we should be to deliver

29. 4 main phases to manage work
Discovery Organize Delivery Monitoring
Usually we just manage work here.
Usually we want to apply UX+Agile here.

30. Discovery Organize Delivery Monitoring
Usually we just manage work at this phase.
Making almost impossible to apply UX Research
and Design properly. “Not enough time”
147 projects/year

31. Discovery Organize Delivery Monitoring
Usually we just manage work at this phase.
Making almost impossible to apply UX Research
and Design properly. “Not enough time”
The outcome: projects or features
poorly connected to business goals
and customer satisfaction masked
with beautiful user interface design

32. How might we organize
work in those “hidden”
phases?

33. 4 main phases to manage work
Discovery Organize Delivery Monitoring
What are our
business needs?
Who’s our
customers?
How are they’re
journey with us?
What should we
eventually do to
achieve business
goals?
What should we
do to put it live as
fast as we can?
How to make
sure we have all
dependent teams
synchronized
How to make
sure it respect
brand guidelines?
What are the
hypothesis we
should keep?
Do we have a
specific date for
that work to be
live?
What is really
urgent?
Which teams can
start to work on
that and when?
What’s not
important now?
Is it giving the
expected results?
If yes, should we
make more of
that?
If no, should we
dig to understand
better?

34. #ProTips

35. #1 Avoid BDUFING!
Treat your “projects for the year” as hypothesis of value generation.
Prioritise it, and prove it’s value before commiting to it.
#1 Avoid Big Design Up Front

36. #2 Make it visual
Visualizing our “147” Hypothesis is a great start

37. Organize Delivery Monitoring
Dump fearless
Discovery

38. #3 Manage work in process
Organize Delivery MonitoringDiscovery
Commitment
point
Discard Delivered
Limit Work
in process
Select and commit to work based on
perceived added value vs team’s real capacity.

39. #4 make it understandable
Add some information to this hypothesis
as they move on from discovery to delivery

40. Title of the hypothesis
Business needs that it address
For whom are we doing that?
Which teams are impacted?
Do we have a deadline?
Pieces of information
on post-it’s to make it easy
to understand / prioritise / dump
If information is to blurred,
probably you can dump it

41. #5 use UX tools at the right moment
Instead of focusing all your efforts on the delivery,
use UX to help you decide

42. Discovery Organize Delivery Monitoring
Medium to high
fidelity prototypes
Usability testing
(for new features
on medium to high
fidelity prototypes)
Heuristic
evaluation
Taxonomy
Personas
Customer journey
map
Focus group
Qualitative/Quantit
ative surveys
Field studies /
Observation
User interview
Paper prototyping
Design Sprint
Card sorting
Focus groups
Evaluative surveys
Low fidelity
prototypes
Usability testing
(on low fidelity
prototypes)
Design Sprint
Co-design
Heatmaps
User recorded
sessions
Analytics
Surveys
Bug review
Usability tests (on
existing features)

43. #6 measure progress
Are you being good on dumping stuff? What’s the time needed to first
prototype? What’s the time needed to deliver? Do you have capacity issues?
Organize Delivery MonitoringDiscovery
Commitment
point
Discard Delivered
Time to market
Discard rate
Time to first prototype
Lead time

44. #7 Restart
Organize Delivery MonitoringDiscovery
Discard
GOALSUse learnings to feedback strategy, discover new hypothesis,
deliver delighting stuff, monitor.

45. #8 review your process
Feedbacks are not just from users to features.
From team to process is equally important.

46. Resources:

47. Want some
extra content?
.com/tiagorosa
Consider subscribing