Service Design Q&A Library
1 min read
What's a good structure for a Service Design portfolio?
Back in the day, in my own Service Design portfolio, I used this structure for each project.
The format
- Challenge: Describe in form of a question that starts with “How can we…” what was the problem you were trying to solve.
- Context: One side note about the context which made this project especially difficult, interesting, etc.
- Tasks/activities: give the titles of the activities or tasks you worked on (user research, prototyping, etc.)
- Team: show who else worked on this project, what was their role and what was yours (service design projects are usually team efforts)
- Failures: describe one thing that didn’t go well. This helps you to show humility.
- Learnings: describe one thing that you learned in this project that you will do again in other projects
Length
The idea here is that for each point you will have only one sentence to keep it short and interesting.
Related articles
How to format Microsoft Lists for a course schedule so that it doesn't suck?
In short: with custom JSON code, that you can ask an LLM to help you write, you can adapt how the details of a session in your course look like.
2 min read
How to create a small course hub in a teams channel
In short: Use tabs to link to key documents, and resources. Use Microsoft List as an integration to put the schedule that shows as a list or a calendar.
2 min read
Why I go for alternatives instead of variations when making and testing protoypes
In short: alternatives that are opposing make you learn more than small tweaks.
1 min read