How to start and what to look for

Find the pieces before the puzzle. Source : Giphy

If the design phase is like putting together the pieces in a jigsaw puzzle, the investigation phase is like gathering these pieces beforehand. The pieces you find will serve as the baseline of what you can work with, and the way each piece is shaped will hint at how to correlate and connect the constraints for the design phase.

Here are some of the areas that I’ve found to be simple and informative to start on, and what to look for in each.

  1. The higher-level goal overarching your assigned task
  2. History
  3. Timeline
  4. Existence of technical constraints
  5. Your partners

Step 1 : Understand the higher-level goal

What you are tasked with likely falls under a bigger agenda. Find out how your work builds towards that agenda, so that you can take into account how to impact the short term outcome for the delegated task and the long term outcome aligning with the higher-level goal. This increases the likelihood of making your output more lasting and relevant further down the road.

Potential starting points:
Vision memo, Project wiki or spec, Conversations with project lead.

Step 2 : Investigate the history

Catch up to speed on what has been discussed so far, what has been attempted, and what has & has not remained in the current state. It’s valuable if you are able to identify what hasn’t worked and the reasons behind it. And when doing so, look beyond the idea details. Try to dig in and understand the background context behind why that idea did’t work. Then when you come up with another idea that may come off as a similar solution, you can find your way around its blocker.

Potential starting points:
Previous design proposals, Telemetry data and shifts in metrics before & after related changes, Conversations with designers & partners who have been through previous idea pitches.

Step 3 : Investigate the timeline

Missing the milestones makes your idea irrelevant. Talk with the project lead, get a sense of the key milestones, and understand how the team’s work is staged per milestone. Then identify where your work would be most relevant and lead to maximum impact. If your work is a blocker for another work to follow, make sure to identify it and take that into account.

Potential starting points:
Project wiki or spec, Conversations with project lead, Update the status of your work at team shareouts for other key stakeholders’ awareness

Step 4 : Investigate existence of any technical constraints

A screw driver can’t be used to bend objects like a wrench can, but it is much more effective in screwing & unscrewing components compared to a plier. You don’t need to know how to code. But having a general understanding of the technical constraints helps you know what you can leverage to effectively come up with a creative solution.

Potential starting points:
There are vast number of content and places to start from, but many of them are difficult to pick up from a quick reading or an overnight studying. I found it to be effective to think of this as a long-term learning process. 
1. Develop a close relationship with your engineering team to be able to discuss ideas freely, and learn what works & doesn’t from every conversation and progress you make together. 
2. If there is a medium that you know you will work primarily on, carve out time to learn about it even if there isn’t a pressing assignment related to it.

Step 5 : Talk often with your partners.

Communicate with your product manager, engineer, design peers, and other key stakeholders you are working with. More you are in sync, more light you can shed into the space. Often times, I’ve found it to be more effective to start with spontaneous on/offline conversations involving everyone rather than starting with 1–1 conversations. For deeper discussions, 1–1 conversations work but doing that from the start can lead to keeping each other in the dark inadvertently.

Source link—-138adf9c44c—4


Please enter your comment!
Please enter your name here