Essentials Every Non-Technical Person Need To Know To Build The Best Tech-Team by Pau Ramon

1,545 views
1,384 views

Published on

In this talk, held at itnig the 8th of May 2014, Pau Ramon shared with us his mistakes and learnings as CTO at Redbooth. His insights can be really helpful for all of us, not only for people that want to build a technical team, but also for people who are actually part of one.

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,545
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
11
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Essentials Every Non-Technical Person Need To Know To Build The Best Tech-Team by Pau Ramon

  1. 1. Building the best tech-team
  2. 2. Management
  3. 3. Management “ To coordinate the efforts of people to accomplish goals and objectives using available resources efficiently and effectively”
  4. 4. WhoamI? CTO at Redbooth ! Twitter: @masylum
  5. 5. Bewareof bullshit • Learn from others • Every company is different • Don’t copy: common sense
  6. 6. Whatisthistalkabout? • Recruitment • Optimization • Growth • Success
  7. 7. Recruitment
  8. 8. Seduction • Go meet interesting people • Interview? Go for a coffee! • Talk and listen, seduce and be seduced
  9. 9. HireeHirer
  10. 10. WhoshouldIhire? Bet on motivated generalists. ! Knowledge is easy and fast to acquire, talent is not.
  11. 11. WhoshouldIhire? Invest for the long term: Experience within the company is the most valuable asset
  12. 12. Optimization
  13. 13. Throughput
  14. 14. Stablesystem SystemInput Output
  15. 15. Idlesystem SystemInput Output
  16. 16. Saturatedsystem SystemInput Output
  17. 17. Washingdishes Saturated Idle Soaping Rinsing
  18. 18. Synchronicity
  19. 19. Synchronicity • Inefficient in unstable systems • Less overhead • Not flexible
  20. 20. Synchronicity Soaping Rinsing Soaping Rinsing TeamA TeamB
  21. 21. Asynchronicity
  22. 22. Asynchronicity • Less waiting time • Requires queues • More overhead • More flexible
  23. 23. Asynchronicity Soaping Rinsing Soaping TeamA TeamB QueueQueue Soaping
  24. 24. Queues
  25. 25. Queues • Appear in saturated systems • Measurable • Ordered
  26. 26. LIFO:LastInFirstOut C B A
  27. 27. FIFO:FirstInFirstOut C B A
  28. 28. Prioritization • Agreed and arbitrary • Unfair but help focusing • Add age to the mix to avoid starvation
  29. 29. MultipleQueues
  30. 30. Multiplequeues Alice Bob Chris
  31. 31. Multiplequeues 1day 5days! 12hours Alice Bob Chris
  32. 32. Singlequeues Alice Bob Chris
  33. 33. Trytoalwaysgofora singlequeueand multipleconsumers
  34. 34. Optimize! • Go asynchronous • Measure your queues • Identify your bottlenecks • Allocate people accordingly
  35. 35. Growth
  36. 36. WhoshouldIhire? • Avoid Single Point of Failures • Start getting specialists but not too many • Cultural fit is important!
  37. 37. Whenhiring, getyourteam involved
  38. 38. Success
  39. 39. Choosetwo: Scope Resources Time
  40. 40. Motivation • Bad: Carrots and sticks • Good: Autonomy, Mastery, Purpose http://bit.ly/1eVm5pI
  41. 41. Motivation • Encourage Collaboration over Competition • Set team goals, not individual • Let the team be the judge
  42. 42. Rules!
  43. 43. Norules
  44. 44. Rules
  45. 45. RulesandCulture • Rules have to be agreed • Culture is the enforcer: Let the team be the police • After a mistake, think of a rule that could’ve prevented it
  46. 46. Teams CoordinatorCoordinatorCoordinator Vertical collaboration on a given project
  47. 47. Coordinators • They are doers • They are responsible for the performance of the group • They are the spokeperson of the team
  48. 48. That’sallfolks Thanks

×