Designers need to be flexible. We not only have to flex our process to accommodate different team configurations, but also adapt our workflow as the project unfolds.
When we have completed the designs of a project, we have only done half of the work.
The real challenge starts when developers start poking around and asking questions about our designs, and when quality assurance analysts start thinking about use cases we couldn’t foresee.
Instead of feeling frustrated when product managers cut down product features to get to an MVP, designers could turn it into an opportunity to increase the quality of the experience within the feature set we are delivering.
Our empathy, our focus on users, and our passion — those are valuable resources we can use to inspire developers and help them understand not only how a certain feature is supposed to work but how it’s going to impact people’s lives.
In certain companies, developers are not involved in early concepting, design explorations, and strategic product discussions with product managers. How can we help bridge that gap and help them understand the bigger picture of what they are building?
More on Process
It’s helpful to perform a ‘dry-run’ of any new process or activities with a small group. You can get an understanding of what to expect from the eventual participants and identify any weaknesses in advance of the sprint.
by Robbie Farrell
in Design sprint tips from 7 facilitators at Booking.comby Robbie Farrellin Design sprint tips from 7 facilitators at Booking.com
in Design sprint tips from 7 facilitators at Booking.comby Robbie Farrellin Design sprint tips from 7 facilitators at Booking.com
Change management is not about writing a bunch of policies about process. It’s deep design work to establish new operating practices for our teams.
by Michelle Morrison
in Process vs Practiceby Michelle Morrison in Process vs Practice
in Process vs Practiceby Michelle Morrison in Process vs Practice
Agenda, people! – Keeping things tight and to a central theme will mean that the meeting can be as short as it needs to be whilst also keeping people on track.
by Luis Ouriach
in How to run a successful design meetingby Luis Ouriach in How to run a successful design meeting
in How to run a successful design meetingby Luis Ouriach in How to run a successful design meeting
Many designers work on gut feeling and do what feels right, but in an open setting of co-creation, it’s important to explain design decisions.;
by Dennis Hambeukers
in The Secret To Making Design Co-Creation Workby Dennis Hambeukers in The Secret To Making Design Co-Creation Work
in The Secret To Making Design Co-Creation Workby Dennis Hambeukers in The Secret To Making Design Co-Creation Work
Setting context is important when asking for feedback. If you don’t, each person can have a different understanding of how far along your design is and also be keen on giving feedback to different parts of the design.
by Sungjoon Steve Won
in Constructive vs Destructive feedbackby Sungjoon Steve Wonin Constructive vs Destructive feedback
in Constructive vs Destructive feedbackby Sungjoon Steve Wonin Constructive vs Destructive feedback
See all from Process
Subscribe to our newsletter for weekly design highlights!
I promise, I won't spam you.
