uxcampams

Improve your design process

Roy — Sat, 10 Sep 2016 15:23:57 +0000

Sub title

with reggae music

/sites/default/files/styles/large/public/20160910_155708-1.jpg?itok=CvyF1SRg

Nice interactive session by Peter, self-confessed design process freak. Starting with a trick question on ux deliverables: you want to at least influence what's in project plans and estimates as well!

It's good to have a well defined design process. It enables to take care of solving the known problems in a repeatable and effective way. Which leaves you with more time and resources for tackling the as yet unknown problems where you probably have to improvise your way to a solution.

Document your design process first. Then improve it using this formula:

1. I will [do something]
2. Together with [another role]
3. And we will change [a part of the process]
4. To improve [a success metric]
5. Before [a deadline]

Tags

process

uxcampams

Prioritize your work as a product designer

Roy — Sat, 10 Sep 2016 15:00:20 +0000

Sub title

trade-offs. you have to make them

/sites/default/files/styles/large/public/20160910_145514-1.jpg?itok=AQh8yAAq

Thank you Derec for opening up an interesting discussion on prioritizing product design work. The group widenend the scope a bit (no surprise there) and focussed on how we can help stakeholders express the impact, relevance of their idea compared to all the other new feature or improvement proposals.

Look up: RIC/E, OKR's and maybe even NPS.

Tags

product

uxcampams

Maintain the illusion of freedom

Roy — Sat, 10 Sep 2016 11:56:14 +0000

Sub title

components before templates

/sites/default/files/styles/large/public/20160910_130137-1.jpg?itok=1pZMAqtw

Simon showed which decisions he had to make to balance editorial and design freedom with keeping the CMS and design system behind it maintainable.

There was consensus in the room that all CMS's suck. Glad we could establish that.

Simon combines frontend dev and interaction design skills which enabled him to do this website build mostly on his own and stay in control, keeping the number of components and exceptions on them low. Well done!

Tags

design system

uxcampams

Kill lorem ipsum

Roy — Sat, 10 Sep 2016 11:00:41 +0000

Sub title

uxcamp session 1

/sites/default/files/styles/large/public/20160910_123956-1.jpg?itok=lzcQBKwW

Rob facilitated a short workshop on how to find your main content requirements. Called the Task Canvas it starts from a single user goal paired with a relevant organisation goal. For the user there are questions that need answers. For the organisation there's desired outcomes. At the intersection of those you can then identify the content you need to support the user task and organisation goal.

Reminiscent of the Core Model

Getting your content requirements straight is essential. How else to know what to design for in the first place. Killing lorem ipsum is a worthy goal!

Tags

uxcampams

content strategy