Designer handbook
Slaying Pixels: Our Philosophy to Design.
Our philosophy to design, tools of the trade, design processes, and culture ideals.
Process
A six step process for larger projects, a shorter go-to for small projects, and sprints to assist when needed.
Step 1 – Read and contribute to A3
Understand the objectives; answer the questions:
- What problem are we solving?
- Who has this problem?
- What do we want to achieve?
Step 2 – User Experience Research
Become the subject matter expert.
- Has someone solved this problem before?
- User interviews
- Surveys & market research
Step 3 – Rapid Ideation
Sketch and wireframe lots of ideas, quickly.
- Storyboarding / user journey (flow chart)
- Information architecture
- Sketch/Adobe XD is fine, but not pixel perfect
Step 4 – Prototyping
Focus your efforts – may shoot you back to step 3.
- Make full use of Sketch & Invision
- User testing (internal/external)
- Start looping in devs
Step 5 – Final Prototype
Get it pixel perfect and ready for presenting.
- An organized, symbolized sketch file Think of your fellow and future designers – make sure to place on our design Google Drive
- Complete Invision prototype Clickable and inspectable for css, with dev notation for anything that may be ambiguous
- Update A3 of expected visuals
Step 6 – Dev Kickoff
Our involvement doesn’t end with the demo at dev kickoff.
- Be available for dev questions
- Gitlab QA nearing launch
- Follow up with results after launch
Smaller projects
Sometimes there just isn’t enough time to go through a long process. For a smaller project, the steps above may be overkill and cumbersome, so on smaller projects we jump in as fast as possible. Typically this means hopping straight in to Step 3 or 4. We still make sure it is shared on our Google Drive team folder and go through at least one round of peer feedback via Invision before shipping it.
Sprints
Every so often a design challenge comes along that is far less defined than usual. It requires a brainstorm as a team to kick it off – a design sprint. Here at Fullscript we have adopted a 4-day process:
Choose
Choose from a library of 160+ evidence-based templates.
Customize
Customize your template to fit the needs of your patient(s).
Save
Save your template as a starting point for future patients.
Share
Share your template with colleagues on your account.
A note on problem solving
Be confident and iterate. You’re a designer at Fullscript for a reason – you have an eye for it, and understand what makes for a good and bad user experience.
Being confident means asking the right questions, and being data-informed (see Data vs Gut); but it can also means that when you don’t, you are able to iterate, test, then choose the best route instead of designing in circles. Be willing to toss out an idea if it leads to a dead end. Strong opinions, loosely held.