Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Design documentation & more

B01e7082c79ef572005eabc03421aa87?s=47 Hardik Pandya
November 16, 2019

Design documentation & more

B01e7082c79ef572005eabc03421aa87?s=128

Hardik Pandya

November 16, 2019
Tweet

Transcript

  1. Designer @ Google Search Twitter @hvpandya Hardik Pandya Documenting Design

    & more
  2. Products I work on Searchbox Suggest The Google Homepage Intro

  3. None
  4. None
  5. None
  6. None
  7. My story

  8. Shift to a large organization

  9. ⬆ Concurrently ongoing projects & workstreams intertwined with each other

    Startups → BigCorp
  10. Startups → BigCorp ⬆ People in my direct team &

    peripheral teams(+) across the organization
  11. Startups → BigCorp ⬆ Information decentralization: Siloed discussions & isolated

    comms
  12. Life at BigCorp Product surface

  13. Life at BigCorp Surface B Surface A Surface D Surface

    C
  14. Life at BigCorp Surface B Surface A Surface D Surface

    C
  15. Life at BigCorp Surface B Surface A Surface D Surface

    C 6 week release cycles Higher org priority Faster releases Lower org priority Not currently staffed Working on their vision Team in TLV +8h Has a very opinionated Program Lead Outdated stack, revamping Team in NYC +3h
  16. Life at BigCorp Surface B urface A Surface D Surface

    C ek release cycles gher org priority Faster releases Lower org priority Not currently staffed Working on their vision Team in TLV +8h Has a very opinionated Program Lead Outdated stack, revamping Team in NYC +3h Surface E Suddenly prioritized
  17. Life at BigCorp Surface B urface A Surface D Surface

    C ek release cycles gher org priority Faster releases Lower org priority Not currently staffed Working on their vision Team in TLV +8h Has a very opinionated Program Lead Outdated stack, revamping Team in NYC +3h Surface E Suddenly prioritized
  18. None
  19. It’s not all messy though Communication challenges are the byproduct

    of massive scale of the org But massive orgs also build global products
  20. ⚠ Product design narrative originated from a different stakeholder and

    a different artifact, often lost in translation Day to day work
  21. ⚠ Couldn’t command equal stakeholdership in the larger vision despite

    equal thought partnership Day to day work
  22. ⚠ Brought value to my team and teams(+), but couldn’t

    demonstrate it at scale Day to day work
  23. And at a more personal level... Day to day work

  24. ⚠ Couldn’t weave a narrative post facto at perf review

    time Day to day work
  25. ⚠ How would I develop my portfolio? Day to day

    work
  26. ⚠ How would I develop my portfolio? Day to day

    work
  27. So what was I doing differently? Day to day work

  28. Sharing contextless mocks assumed that the problem and constraints were

    well understood & established Problem 1
  29. Mocks demonstrated fidelity of the outcome but failed to demonstrate

    fidelity of thinking Problem 2
  30. Mocks lacked the narrative Scoping the problem → Exploring considerations

    → Making a recommendation Problem 3
  31. Design framing was outsourced to a different stakeholder, proxied by

    their artifact, leading to a game of Chinese whispers Problem 4
  32. Vanilla mocks & screens are an inadequate manifestation of one’s

    value, voice, influence and work.
  33. It was no longer enough to just do the work.

    Owning the narrative around it and socializing it became just as important. Life at BigCorp
  34. It was no longer enough to just do the work.

    Owning the narrative around it and socializing it became just as important. Life at BigCorp Basically my work needed body and legs.
  35. It was no longer enough to just do the work.

    Owning the narrative around it and socializing it became just as important. Life at BigCorp Basically my work needed body and legs.
  36. How do we do that?

  37. How do we do that? Document your work (all of

    it) and create design artifacts
  38. Premise setting HMW CONSIDERATION FRAMEWORK RECOMMENDATION CRIT Figma file Design

    artifact
  39. There’s no one-size that fits all But I have a

    simple framework to get started...
  40. Get informed Create Socialize 1 2 3 Design documentation

  41. Get informed Create 1 Socialize 2 3 Set up the

    context Do the actual work Sell the work Design documentation
  42. Get informed Create Socialize 2 1 3 Design documentation

  43. Internalities Find where the org’s thinking is (what is the

    higher order strategy / directive?) Identify who the main stakeholders are (who has strong opinions about this?) Figure out the constraints spectrum (which ones can you break?) Design documentation > Get informed
  44. Externalities Identify research gaps (what do we not know?) Competitive

    analysis (how are others doing this?) Market trends & behavior shifts at scale (what do major market movements tell us?) Design documentation > Get informed
  45. Design documentation > Get informed Thorough brainstorms with your trusted

    xfn partners beat a design sprint & all the diamonds.
  46. 2 Get informed Create Socialize 3 Design documentation

  47. Problem definition & scoping Design documentation > Create

  48. Problem definition & scoping ‍ Broad array of explorations Design

    documentation > Create
  49. Problem definition & scoping ‍ Broad array of explorations ⭐

    Audit & recommendation Design documentation > Create
  50. 2 3 Get informed Create Socialize Design documentation

  51. Online first, and Offline next Design documentation > Socialize

  52. Design documentation > Socialize Soft share-out over email to your

    team & team+ ✅ Invite first-order feedback ✅ Give people time to review on their own time
  53. Design documentation > Socialize But... People have low attention span

    People have competing priorities Reading in-depth material takes people time and effort
  54. But... People have low attention span People have competing priorities

    Reading in-depth material takes people time and effort Design documentation > Socialize “As per my last email...”
  55. Design documentation > Socialize Sharing artifacts is how you get

    visibility. In-person reviews are how you get buy-in.
  56. In-person reviews Design documentation > Socialize

  57. Design documentation > Socialize UX peer review first In-person reviews

  58. Design documentation > Socialize UX peer review first In-person reviews

  59. Design documentation > Socialize Roadshow next In-person reviews

  60. Design documentation > Socialize Invite PMs, PgMs, TLMs, UX leadership

    and other execs in a room all at once ...you present your idea...
  61. Design documentation > Socialize Don’t

  62. Design documentation > Socialize Don’t Seriously.

  63. Design documentation > Socialize Don’t. Seriously.

  64. Design documentation > Socialize Resolve locally before you presenting collectively

  65. Design documentation > Socialize ✅ Preemption over a ⛔ Grand

    reveal
  66. Design documentation > Socialize Set up first stakeholder presentations to

    seek buy-in & not a resolution
  67. Premise setting HMW CONSIDERATION FRAMEWORK RECOMMENDATION CRIT Figma file Design

    artifact
  68. 2 Get informed Create Socialize Design documentation

  69. 2 Design documentation Create

  70. 2 Design documentation Create

  71. Socialize, discuss, get feedback, iterate & maintain Keep it alive

  72. Vision roadmaps: Longer shelf-life, lower tactical value, high POV, low

    impact Project Doc: Mid shelf-life, high tactical value, mid POV, high impact Reference Doc: Longer shelf-life, lower tactical value, mid POV, high impact Types of artifacts I typically make
  73. None
  74. Some tactical tips ✅ Use a slide deck for documentation

    ✅ Mention your name and LDAP ✅ Status flags – ‘Early explorations’, ‘Approved’, ‘In experiment’ ✅ Table of contents ✅ Make post-audit recommendation stand out
  75. None
  76. Great organizations have the tendency to recognize and elevate talent.

    Work hard.
  77. @hvpandya me danke!

  78. @hvpandya me danke! not me ¯\_(ツ)_/¯