Sociocratic decision making Introduction Quite often the challenges with making decisions are the following: It’s difficult to get all parties involved aligned towards a decision. Once a decision has taken, some degree of uncertainty remains if people actually support the decision. Welcome to sociocratic decision making Sociocratic decisions differ from autocratic (no to low support, but fast decision making), democratic (with majority vote) (at least 51% vote support), and consensus (broad support, but time-consuming process). […]
Listening to podcasts Podcasts are a great way to learn and to listen in to conversations with people you’ve might have heard of, but you don’t really know who they are. Podcasts are a tremendous source to learn about new topics – virtually anything! I’ve been listening to podcasts for a while, mainly topics relevant to my professional occupation – but there are many many podcasts out there! I listen to podcast when commuting to […]
For the readers: A reference for organising retrospectives is the book “Agile Retrospectives – Making Good teams Great”, by Esther Derby & Diana Larsen. They describe the main steps of an agile retrospective. The prime directive of retrospectives has been formulated by Norman Kerth in his book “Project Retrospectives: A Handbook for Team Reviews”. “Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they […]
There are many manifestos written, principles and values. I sympathise a lot with this: Imagine… everyone able to work consistently at their best: Individuals, teams, between teams, across the organisation Right conversations, right people, best possible moment Needs anticipated, met at just the right time Source: A True North for Lean-Agile?
Een belangrijk element in een continue verbeteringsproces is een continue cyclus van plannen, uitvoeren, verifiëren en bijstellen. De uitdaging is om deze cyclus herhaaldelijk te blijven uitvoeren, zodat de zin voor kwaliteitsverbetering een continue gegeven wordt. De indeling van deze stappen zijn de stappen zoals aanwezig in de wetenschappelijke methode: het formuleren van een hypothese, het uitvoeren van een experiment, en het evalueren van de resultaten (om de hypothese juist of fout te verklaren). Deze […]
Playing Lean is a business simulation, in the format of a board-game to learn about lean startup principles and practices. The following facilitator tips are based upon those experiences. Some of the tips are more advanced (meaning these take time to prepare). You might not agree with all recommendations, but hey it’s up to you to try 😉 (as an experiment)
Incredible story before the 2000 “dot.com” boom illustrating the lack of customer development. Lesson learnt (by Steve Blank) – Business plans are the leading cause of startup death – No Business Plan survives first contact with a customer – Rapidly changing markets require continuous business model iteration/customer development – Your ability to raise money has no correlation with customer adoption Source: http://www.businessinsider.com/no-business-plan-survives-first-contact-with-a-customer–the-52-billion-dollar-mistake-2011-1
Lean Camp is an unconference on topics as Lean Startup, Lean UX, Design Thinking, Product design, etc. I like unconferences as each attendee has the opportunity to participate (you can propose a topic), and the interactivity is really high. I participated in a discussion on integrating UX in agile development team; and how to maximise learnings from serious games – for example Playing Lean.
Lean Startup Lean Startup is a method, an approach for developing businesses, products or services. The method has been developed and made popular by Eric Ries. In September 2008, Ries first coined the term on his blog, Startup Lessons Learned, in a post titled “The lean startup“. His book “The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses” was published in September 2011.
THINK: assumptions and hypothesis Instead of expressing “requirements” we consider assumptions and we declare hypothesis statements. A hypothesis statement is a way of expressing assumptions in a testable form. Reality often shows that the creators of a product or services are not sure what a user actually needs or wants, or how it should work, with regard to the user experience. But quite often organizations, or companies simply proceed with their idea for functionality or […]
In any context, objectives (or outcomes) are important as they give guidance or direction; instead of only focusing on solutions. (Solutions in the broad meaning: a product or service, an improvement, a feature, a functionality, …) Quite often, solutions are proposed or defined without an objective in mind. To reach a certain objective, multiple solutions are possible. We want to track progress with respect to objectives, not only solutions. When teams are given an objective, teams […]
Lean UX = applying Lean and Lean Startup principles to User eXperience. Remove waste from the UxD process Too much too often product (software) design and development is document-driven. With the agile manifesto and principles in mind, we want to focus on creating great and valuable products (software) and releasing these early and often to get valuable end-user feedback, in order to improve our products (software) iteratively and incrementally. Forget about the overload of UxD […]
Lean UX is about apply lean principles to User eXperience. Why? There are 2 main observations: Bad UX. Failed products. Unfortunately, there are still too many (software) products and services built and released on the market, that do not fit the customers’ needs. This is a long lasting pain in software development. Nowadays thanks to modern web & mobile technologies, possibilities are endless. But than again there are still too many useless, badly designed, wrongly understood, misfit […]
Once upon a time, there was a marketing guy, with great ideas for a new software application. He hired a business analyst, who described all those ideas in formal fully documented business requirements (including use-cases, business rules, exceptions …). This deliverable was handed over to a User Interface / User Experience expert who created detailed the User Interface (including wireframes, site maps, screen flows, mock-ups,…) and described all the user interactions. Next, a functional analyst […]