5 Benefits Of Simplicity

I love things that are simple. By “things” I mean almost everything, from processes and tools to machines, rules and businesses.

Simplicity generates a virtuous chain of situations and benefits that I drew here:

5 Benefits Of Simplicity

Bringing simple solutions and processes that are easy to understand for others and start this virtuous chain is not always easy. It’s actually more complicated than coming up with a complex solution.

Humans tend to add complexity to things, specially in a work environment where it’s frequent to see people thinking that adding complexity will show others that they are actually working. It takes some experience to first be self aware when one is adding unnecessary complexity and then be humble enough to just add what is needed.

Also some people associate simplicity with incompleteness. The simple solutions and things I’m talking about here assume you’re trying to come up with a complete solution, something that includes everything that needs to be included. This is also a place where people tend to add complexity.

I hope this was useful to you. If you think of more benefits of simplicity please leave them in the comments below.

Agile Inceptions: 5 tips to make them more efficient

Inceptions suffer from the same problems that affect long meetings full of people:

  1. Having a lot of people in a room like your stakeholders, your team, your boss and your boss’s boss means only one thing: long discussions about opinions and points of view, without real hard data to back those opinions, which make discussions even longer. This of course means you can’t obtain much value for your product after these discussions.
  2. It’s normal to also have people connected via video-conference like Skype or Google Hangouts. It’s 2016 but we still have issues with these types of virtual meetings, specially with internet connections not being as good as they should be. This means you’ll probably have to repeat something many times in order for everyone on the other side of the screen to understand what you’re trying to communicate.
  3. Since there are so many people invited to this event, there’s probably more than one that will be late and you’ll have to do a summary of what has been discussed up to that point, only for that person, but wasting everyone else’s time.
  4. The Inceptions I’ve been to have lasted 5 consecutive days. 5 days! 5 days, with at least 10 people in the room, for 8 hours a day… that’s 400 hours of engineers, designers, project managers and executives. Are you sure you need that much capacity in order to know what product to build and set your initial backlog? Do you really need these really expensive 400 hours?

Continue reading “Agile Inceptions: 5 tips to make them more efficient”

[Book Review] Remote: Office Not Required

Today I finished reading Remote: Office Not Required, by Jason Fried and David Heinemeier Hansson. Jason and David are the founders of 37signals, a company that creates great web applications for collaborating and working. David is also the creator of the ultra popular web framework Ruby on Rails and they both already wrote two books called “Getting Real: The Smarter, Faster, Easier Way to Build a Successful Web Application” and my favorite, “Rework“.

Continue reading “[Book Review] Remote: Office Not Required”