12 Lessons from ThoughtWorks

Pat Kua has a great article up titled 12 Years, 12 Lessons Working at ThoughtWorks. In his first section “Tools don’t replace thinking”, he hits on something that’s true for all entrepreneurs building SaaS products:

Too many times I have witnessed managers implement an organisational-wide tool that is locked down to a specific way of working. The tool fails to solve the problem, and actually blocks real work from getting done. Tools should be there to aid, to help prevent known errors and to help us remember repeated tasks, not to replace thinking.

Here are the 12 lessons:

  1. Tools don’t replace thinking
  2. Agile “transformations” rarely work unless the management group understand its values
  3. Safety is required for learning
  4. Everyone can be a leader
  5. Architects make the best decisions when they code
  6. Courage is required for change
  7. Congruence is essential for building trust
  8. Successful pair programming correlates with good collaboration
  9. Multi model thinking leads to more powerful outcomes
  10. Appreciate that everyone has different strengths
  11. Learning is a lifelong skill
  12. Happiness occurs through positive impact

While some lessons are developer centric, most are broadly applicable. Go read 12 Years, 12 Lessons Working at ThoughtWorks.

What else? What are some more takeaways from the article?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s