Individual point of view and collaboration
I launched a zine! Get Proof of Concept: The 000 Series today. Individual point of view and collaborationIssue 110: Understanding the two modes of work and how they complement
Without question, collaborative document editing for teams building products is here to stay. This shift has to do more with how companies operate than the product development process. When you think of collaborative software like Google Docs, GitHub, and Figma, they took the model of local-first software and make gave more access to people in the org to do work together. 65% of Figma’s users are non-designers, 3x’ing the amount of people using the design tool¹. Collaboration has revolutionized the way work is done. However, what I see get lost in the midst for doing work together real-time is time for people to think and develop a point of view. Frank Bach, Principal Product Designer at Headspace articulated this well in a tweet. ![]() My hypothesis is by increasing the contrast of developing your personal point of view combined with collaboration can result in better team outcomes. Let's cover some details of each one and what you (and your team) can do to mature these practices. Individual point of view (POV)Having a strong point of view develops conviction what you believe in. Having a strong point of view doesn’t mean you need to act like the former CEO of Bolt. It’s about shining a beacon on what you believe and your point of view. People who have a strong POV can also be very open to collaboration (avoid binary thinking). It's a way to share your observations on and your ability to pass on what you learn and share your point of view faster while embracing diversity of thought. Pitfalls of individual POVThough a strong POV is important, being open to integration points and feedback is key. This could be design critique, a pull request on GitHub, or product review. It's critical to remember to share your POV as you're working on it to ensure it can be integrated. Tools I use for individual POV purposesI use tools that are local-first or physical, and I may share snippets of the content to form an artifact vs. sharing the the entirety as an artifact. Some tools I enjoy:
CollaborationCollaboration is the action of working with someone to produce or create something. Whether it's a sports or product team, teamwork and collaboration is crucial in teamwork and achieve a shared outcome. As the African Proverb goes, "“If you want to go fast, go alone, if you want to go far, go together”. The super power of collaboration is thinking through ideas together, getting inputs, and unstuck. When you're stuck or needing a lot of inputs, there is no better way than putting everything on the desktop to work together. I'm a huge believer in pair programming/design, workshopping, and diverging to de-risk. Pitfalls of collaborationThe biggest challenge in collaboration is what I call “The Convergence Melting Pot.” This phenomenon occurs when individual points of view get lost in collaboration and all inputs blend together. Avoid shipping "yes and…" whenever possible. Over-collaboration can result in unclear next steps or decisions. Who out of the entire group is the decision maker to move the work forward? Who will be held accountable for the outcomes? Tools I use for collaborationThe properties of great collaboration tools is a shared canvas, the ability to comment, and early visibility. A few collaborative tools I enjoy are:
Using both effectivelyDeveloping an independent POV and collaboration are effective tools to use and works better when the contrast between them is clear. Here are two suggestions on how to use the two effectively without blending them. Inputs over infusionWhat occurs frequently in collaboration is what I like to call "the melting pot effect." Like a fondue, a melting pot infuses and mixes everything as one thing. What results is what were clear inputs are blended in a something less intentional. Don’t build the car Homer Simpsons tried to build. Instead of a Convergence Melting Pot, keep in inputs clear and work together to make decisions. The power of collaboration occurs when there are inputs and diverse points of view. Without diversity of thought, you’re no considering everything. Instead of a melting pot model, I prefer an input model. Build your POV docOn habit I'm forming is building my POV doc on topics to share with people. It's specific and personal—used for an input for people to consider and make decisions. The nice aspect of a POV doc is often we are verbalizing our point of view without it being memorialized anywhere. I call the POV doc my Credo, the latin word for "I believe." Your POV/Credo can be an input that influences a decision made and there is a clear correlation to it. When crafting a POV doc:
Your POV doc can be a high level concept, such as “Visual Programming” or can be part of a Design Brief you generate. Develop a POV, share before collaborating, and decideIn a world of easy access to multiplayer and real time collaboration, it's easy to forget to establish your point of view. Developing your point of view and collaboration are both important. Make time to balance both and use them when they are most valuable. I highly recommend reading the book Design at Work by Joan Greenbaum and Morten Kyng. Warning, it’s a great ready but heavy—making Thinking Fast and Slow seem breezy like a one-sitting read of a Goosebumps book. Collaboration isn't a nice-to-have, it's essential. That said, get the right inputs, ensure perspectives are heard, and make the decision.Maximize it by developing your own POV to understand your perspective and those of your colleagues. Tweet of the week![]() Hype linksNotes
1 Yes, Peter, we know it’s a drawing tool. (I’m trolling, Peter. We love you and Happy Birthday.) 2 Actual pen and paper, not an app Enjoy this newsletter? Please consider sharing it with friends, or subscribing if you haven’t already. I appreciate it! Sincerely, DH |
Older messages
Design software's circle of life
Sunday, September 18, 2022
Issue 110: Reactions to Adobe acquiring Figma and why it'll be okay
Enter Dynamic Island, a major hint at Apple's Extended Reality (XR) strategy
Sunday, September 11, 2022
Issue 109: Why a funky new software design pattern on the iPhone 14 Pro might hint at XR
Practicing note rewriting
Sunday, September 4, 2022
Issue 108: Tending to previous writings to keep valuable notes
Spotlight: Brooke Clifton
Sunday, August 28, 2022
Issue 107: Interview with Brooke, Staff Product Designer at Public
Getting things done with OmniFocus
Monday, August 22, 2022
Issue 106: A look at to-do apps and sharing what works for me
You Might Also Like
Business as a platform
Sunday, March 9, 2025
Issue 236: Applying business to your craft ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
A Guide to Timetravels
Sunday, March 9, 2025
Our past and present selves have never been separate entities but rather interwoven narrators. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
The New Kitchen Trends on Our Radar
Thursday, March 6, 2025
View in your browser | Update your preferences ADPro Kitchen Confidential We at AD PRO see the kitchen as a bellwether for the rest of the home—a place where technology stays a couple of steps ahead,
🐺 How to kick start your PR efforts.
Wednesday, March 5, 2025
Lessons from a veteran publicist. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
How Rita Konig Gets Clients to Take Risks
Tuesday, March 4, 2025
View in your browser | Update your preferences ADPro It has been a career-defining few years for Rita Konig. First there was the British interior designer and author's Create Academy course, which
#497: Color Palettes and Generators
Tuesday, March 4, 2025
How to fix a broken color palette, accessible color combinations, color names and palette generators. Issue #497 • Feb 28, 2025 • View in the browser Smashing Newsletter Pryvit! Smashing Friends, How
180 / Make your everyday browsing ridiculously beautiful
Monday, March 3, 2025
Product Disrupt Logo Product Disrupt Half-Monthly Feb 2025 • Part 2 View in browser Welcome to Issue 180 Last year I teamed up with two of my close friends on a side project we're all obsessed with
Accessibility Weekly #438: When to Use Lists
Monday, March 3, 2025
March 3, 2025 • Issue #438 View this issue online or browse the full issue archive. Featured: When to use lists for better accessibility "When creating HTML content, using lists appropriately is
High touch recruiting
Sunday, March 2, 2025
Issue 235: Long-lasting candidate experiences ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
All Compute Must Flow
Sunday, March 2, 2025
“If I don't have that kind of compute on Day 1, I can't breathe." ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏