Daily, thousands of designers around the world start or join new projects. Despite this, unwillingly or sometimes unknowingly, we are forced to choose the process or method that exhausts the team and ourselves. In addition, of course, let’s not forget the fact this often means that we don’t deliver products as we originally anticipated.
This article aims to champion the need for a combined method of Design Thinking and the Dual-Track Agile methodology that supports huge numbers of creatives working across a diverse portfolio of product and service propositions for over two decades.
Disclaimer: As the topic itself could have…
800-clap and massive thanks for sharing the story especially recognition of superpowers that some of us are grateful enough to discover in our early career and thrive the change within the organisation we work for.
This may sound obvious but not having input from an end user means you will be missing valuable feedback on how they would anticipate using the system. If your team is only getting input from users before the product development starts or after it’s fi…
Fantastic article @Janaka!
It great to see more design-led articles about Agile. How did you integrate input from the user into your DoD definition; and its impact on the delivery?
Throughout the Design at Scale (DaS®) mentoring, I have observed very little understanding of “the definition of done” amongst designers. It’s no wonder — in 2019 while working with 27 different teams I asked what their Definition of Done (DoD) is and how the design represents itself alongside other disciplines; the answers were shocking.
Before we dive into details, fun facts and the bitter truth, let’s cover the basics of what the DoD in Agile development stands for.
Definition of Done is an agreement on which basis the Scrum team defines the optimal software development deliverables to be good enough.
“Documentation is like sex: when it’s good, it’s very, very good; when it’s bad, it’s better than nothing.”
— Dick Brandon
Welcome to the last the fifth articles of this series. Over the last four weeks, we went through the history and definition behind this Confluence structure. Helping the colleagues with a business mindset to have an extra lens on the product and development through the supporting parts of Hello, Business and Research sections. Followed by the folks with a design mindset that are organised around the Content, Experience and Design Section to help the definition of the product. This…
“Design is a conscious and intuitive effort to impose meaningful order. Design is both the underlying matrix of order and the tool that creates it.”
— Victor Papanek
In the last article, we look at the structure that increases transparency across the business. This article aims to answer all the questions related to design sections, namely Content, Customer Experience and User Interface Design.
“Transparency is the new objectivity.”
— David Weinberger
In this latest article, we look at the structure that increases the transparency across the product team. There is no better place than the business section represented by three subsections––Hello, Business and Research.
“If you can’t describe what you are doing as a process, you don’t know what you’re doing.”
— W. Edwards Deming
Welcome back. In the last article, we discovered the “Power of One” and how it shapes the thinking behind design delivery within an organisation. This article aims to answer the questions around the Confluence structure that empowers product teams. In other words, the continuation of the journey of creating one single ecosystem for product design delivery.
“If you want to build a ship, don’t drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea.”
— Antoine de Saint-Exupéry
I wrote an article and realised that I created a whole study about the subject. After consulting with trusted colleagues, I have split this giant piece into five different parts. Each one of them focusing on a different part of the same subject.
“How the product teams can speed up their product delivery by focusing on a creation and maintenance of single source of…
Gratefulness is the key to wisdom.
I’ve always dreamed about being a mentor and helping people. My fascination with mentoring started at university when I organised and gave my first lecture about Adobe Flash. There were only 3 attendees around the table, but this experience sparked a passion for teaching that has only grown since. Over the years, I’ve been more and more fascinated with how much time is wasted in the process of creation and delivery, so I decided to focus on design integration within businesses.
As my expertise has increased, in particular, I’ve been offered increasing opportunities…