The document discusses common challenges that design teams face when working on projects. It outlines five key challenges: 1) unclear or differing project objectives between stakeholders, 2) uncertain budget ownership and funding streams, 3) design methods and processes being forced onto stakeholders, 4) team members lacking a shared language, and 5) conflicts between user and business needs. For each challenge, it provides lessons learned, such as the importance of understanding stakeholder motivations, expressing value in the stakeholders' terms, balancing user and business needs, and having a shared project language. The document advocates taking a collaborative approach to design that considers all perspectives.
19. What are they talking about?
The business, including the project owner, technical team,
Stakeholders marketing, brand, digital, compliance, product & project managers
The people using the service, including dealer groups,
Users financial advisers, para planners, support staff and investors
The day to day project team, including project owner,
Core team project manager, technical director and designers
CCD Customer Centered Design, this is the same as human or
user centered design
21. Content Audit
Research
Scenarios
Visual Design
HCD Process User Stories
User Pathways Presentations
Information Testing
Architecture
Paper Prototyping
Workshops
User Experience
Principles
Digital Prototyping User Experience Styleguide
Road Map Blueprint
25. What happens when project objectives are unclear &
Challenge number one differ between stakeholder groups?
26. What happens when project objectives are unclear &
What did we learn? differ between stakeholder groups?
To pause, and explain what the implications of proceeding without a shared approach are
Know when to switch from designer to facilitator to navigate towards a shared approach
Take the time to understand the business context and politics within it
Ask each stakeholder what success looks like to them
27. What happens when budget ownership & streams
Challenge number two are uncertain?
28. What happens when budget ownership & streams
What did we learn? are uncertain?
Know who is signing your cheques and get their buy in early
Consider each individual stakeholderʼs motivations for the project
Consider the overall budget influences and strategy, not just your chunk
29. What happens when design methods & processes
Challenge number three are forced onto on stakeholder group by another?
30. What happens when design methods & processes
What did we learn? are forces onto on stakeholder group by another?
Assume theyʼre not on board until youʼve seen the buy in
Express value in their words, youʼre not a sell out if you talk “business talk”
Donʼt design for clients, design with them
31. What happens when team members are without a
Challenge number four shared language?
32. What happens when team members are without a
What did we learn? shared language?
Develop and agree on a shared language
Be transparent with your process and each activity
Use plain language
Learn the context that youʼre working within
33. What happens when user & business needs
Challenge number five collide?
34. What happens when user & business needs
What did we learn? collide?
Balance user and business needs
Understand and discuss the capacity of the business to support those needs
Step through what implementation looks like with the core team
35. Images of our collaborative framework and how we should use it