11/8/2022 0 Comments Shape designer saasAgain there was a lot of surface area to manage and again the process was surprisingly smooth.īy 2015, we had a core team that had lived through these experiences and hit an impressive stride. We had such good results that we decided to apply the same techniques again in 2012, when we redesigned Basecamp from scratch for version 2.0. I wore the designer and product manager hats on the project and prototyped the breadboarding and scope mapping techniques described in this book to manage the complexity. Shape designer saas password#Besides getting the underlying architecture right, we had to interrupt customers on their way in to the product and make them change their username and password for reasons that weren’t easy to explain. It was a massive technical undertaking with treacherous user-facing flows. We wanted to bundle the products together into a seamless suite with single-sign-on and unified billing. By then we had hired a few more programmers and offered four separate software-as-a-service products. The first test of this idea came in 2009. Shape designer saas software#With one foot in the design world and one foot in the programming world, I wondered if we could apply these software development principles to the way we designed and managed the product. I learned the techniques programmers use to tame complexity: things like factoring, levels of abstraction, and separation of concerns. Working with David and Ruby on Rails made the world of programming accessible to me. Our intense focus on “hammering” the scope to fit within a given time budget was born under these constraints.Īs the business grew, I started widening my skills. We knew we wouldn’t get anywhere with those ten hours of programming unless we used them very deliberately. I executed Jason’s design direction for key features of the app and collaborated with him to fill in details of the concept.įrom the first prototypes in July 2003 to launch in February 2004, David only worked ten hours a week. At the time I was a web designer with a focus on usability and user interfaces. His co-founder, David Heinemeier Hansson, programmed it (and created the well-known web framework Ruby on Rails as a by-product). Jason Fried, Basecamp’s founder, led the design. Today millions of people across all kinds of industries rely on Basecamp as their shared source of truth. It turned out lots of companies had this “information slipping through the cracks” problem. We wanted Basecamp to be a centralized place where all parties could see the work, discuss it, and know what to do next. Information would get lost in the game of telephone between the client, the designer, and the person managing the project. At the time we were a consultancy designing websites for clients. We saw these challenges first-hand at Basecamp as we grew from four people to over fifty.īasecamp started off in 2003 as a tool we built for ourselves. Product managers can’t find time to think strategically about the product.įounders ask themselves: “Why can’t we get features out the door like we used to in the early days?” Team members feel like projects go on and on, with no end in sight. Growing painsĪs software teams start to grow, some common struggles appear: Whether you’re a founder, CTO, product manager, designer, or developer, you’re probably here because of some common challenges that all software companies have to face. Shape designer saas full#It’s also a toolbox full of techniques that you can apply in your own way to your own process. This book is a guide to how we do product development at Basecamp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |