This Week #6: Cultivating good relationships with distributed co-workers, building trust to accelerate growth, and leveling up as a PM when you have extra time
With special guest contributor Hiten Shah!
|Oct 22||Public post|| 3|
Hello and welcome to my humble newsletter, where I attempt to answer your questions and offer candid advice about building product, driving growth, working with other humans, and anything else that’s stressing you out at the office. 🤝
If you’re returning from last week, thank you! If you’re new, nice to have you! Help spread the word by telling your friends to sign up here. 🙏
New this week: The one and only Hiten Shah guest-answering one of your questions. Don’t miss it! 😍
On to this week’s questions…
Q: In the next year, more and more of the engineers and designers I’ll be interacting with will be remote. What advice do you have for cultivating a good relationship with remote engineers and designers?
Since I have very little experience with extended remote work myself, I decided to ask someone who has lived (and written about) this life for years, Hiten Shah, to take this question. He immediately (and generously) agreed. If you don’t know Hiten, he’s a legend. Not only is he one of the nicest, most insightful, and most helpful people you’ll ever meet, he also co-founded four companies (KISSmetrics, Crazy Egg, Quick Sprout, and most recently FYI), has invested in 100+ more, and for years has been putting out loads of rich content about startups, growth , and appropriately . . . remote work. Here’s Hiten’s take:
On a distributed team, you are not in the same physical space, so you don’t get to see each other in-person. You don’t get to just walk up to someone’s desk and show them something, or ask them a quick question. Instead, all of the forms of communication with your team are digital: text, voice, and video.
As a result, remote work leads to an increase in miscommunication.
For engineers and designers, the number one impact of miscommunication is being forced to redo work, and make unexpected changes after you think you are done. All because of something that got lost in translation.
Good relationships with remote engineers and designers require ensuring that there are methods for avoiding miscommunication. You do this by maintaining clarity. Your goal on a remote team is to create a culture where it’s OK to ask for clarification when something feels unclear. This is the key to successfully working on a remote team. Ensuring that everyone is on the same page about exactly what needs to be done.
Here are a few tactical best practices to help you build good relationships with your co-workers:
Always write things down: Whenever you’re on a call, make sure that anything that’s important gets written down. Options that were discussed, decisions that were made and next steps, plus who is going to do them. Go even further for your recurring meetings and have a single document that incorporates an agenda and structured meeting notes of what was discussed each time. It’s also important to fully and clearly document specs to ensure understanding. The more that gets documented, the better.
Screenshare when possible: If you’re talking about work that an engineer or designer is doing, screenshare and go right into the tool where their work and tasks are documented. For example, this could be your ticketing system, a spec document or even an Invision prototype. Work together by having a discussion, going back and forth on the feedback and ideally collaborating in the appropriate tool while on the call. This way nobody has to remember to update things later.
Postmortem everything that’s shipped: Especially whenever larger bodies of work are completed and shipped to customers. Marketing, product, big customer wins. It should all be postmortemed to understand what went well and what didn’t. This way you are constantly assessing how things are going and are able to discuss how to improve them. Having great process and documentation is the key to remote work. You can’t just come up with a process and expect it to work well for you without reviewing and iterating it.
For more remote work best practices that are backed by research that we’ve done, read these 11 best practices for working remotely written by my co-founder Marie.
Q: I work at a Fintech company — how would you think about growth here? Our main challenge is building trust with users (because without that they won’t want to share any of their information), and not being a daily use product.
First of all, let’s talk about a few ways you can build trust with users:
Social proof: If people that you trust are using a product, you’ll certainly be more likely to trust it. Some examples of this in action. How might you leverage data and testimonials from people already using your service to create social proof — how many people are using it, what kind of people, from where, and for what purpose? Help your users immediately see that people just like them are already using and loving your product.
Authority: If someone in authority has vetted a product, you’ll be much more likely to trust it. Some examples of this in action. How might you surface your certifications, approvals, badges, awards, seals, or endorsements from authority figures? How might you acquire more of these? Whatever you have — make sure your users see these early and often.
Guarantees: If something goes wrong, who’s got my back? What’s the downside of giving this product a shot? How might you make your users feel like they’ll be safe and protected no matter what? The Airbnb Host Guarantee was an incredibly powerful tool for getting new hosts over the hump of opening their home up to strangers.
Reputation: This is likely less relevant to your business, but reviews from other users (e.g. Yelp reviews, Uber reviews, Airbnb reviews) are one of the most powerful ways to communicate trust. If many other people have had a good experience, it’s likely you will too. Here’s a good read on this topic.
Great UX: A badly designed site/app immediately introduces suspicion. Particularly when dealing with money. Pay attention to the details — the resolution of images, padding, grammar, performance, and general visual polish. Listen for these issues in user research. Little things can make a big psychological impact here. Watch Joe Gebbia’s TED talk about how Airbnb designs for trust.
Deliver: With our increasing interconnectedness, word-of-mouth spreads quickly. Particularly if you do something wrong. Nothing destroys trust in your brand more quickly. At the same time, if you consistently provide a great experience, and deliver on your promise — that’s how you’ll build real long-term trust. The Amazon Flywheel is a good example of this in action.
With that in mind, three growth levers I’d suggest you explore:
Top-of-funnel: Referrals. For a product that relies on trust, there’s nothing more powerful than an endorsement from a friend. Airbnb had a similar trust challenge, both on the guest side (“stay in a stranger’s home, are you crazy?”) and on the host side (“have a stranger stay in my home, are you crazy??”). Referrals proved to be the single biggest attributable growth lever on both sides of the marketplace. When designing your referrals program, it’s important that (1) the referer has a meaningful incentive, be it cash or credits, that (2) this program is easily discoverable, and that (3) you are incentivizing the right behavior — the referral reward should only pay out once the new user has hit a valuable milestone.
Mid-funnel: Landing page(s). Start building trust from the first moment a user visits your site. How might you leverage some of the ideas I referenced above to instill a strong sense of trust in your product immediately? How might you continue that message throughout the remaining experience? What concerns do people have, at which stage of the flow, and what are you doing to address them? Also, no matter what you’re selling — is the value prop for your product crystal clear? What will compel users to stick around? Make sure to show these pages to real users and listen to their reactions. Continue iterating on this indefinitely.
End-of-funnel: Remind users of the value you’re providing. Without knowing what exactly it is your product is, I’ll take a guess and assume that it’s a “set it and forget it” kind of service, where you sign-up, connect your financial accounts, and good things happen for me. If true, then find ways to remind users of all of the good that you’re doing, and why they’d be fools for quitting. Wealthfront and Betterment do a great of this with a regular email showing me how much interest I’ve earned lifetime with them.
Q: I’ve been a PM at a startup for about 18 months. A few months ago the business shut down, and for a variety of reasons I’ve decided to take some time off to do some extended travel. With months of travel ahead of me, I’d like to use this time to level up my PM game, and I wanted to get your advice on what you think would be the highest leverage learning opportunities during this time.
Truthfully, it’s tough to get significantly better at product management without actually doing product management. No amount of reading, classes, or discussions will be as good a teacher as doing the actual work. However, having time to step back, to process, to read deeply, and to build complementary skills is a rare gift and can indeed accelerate your progress once you return to the job. Here are a few things I’d suggest for your time off:
Follow your energy: What have you been yearning to do or learn while employed, but have been unable to because you’ve been too busy or lacked the energy? Maybe it’s learning to design, or learning to code, or getting better with data. Do that. Do the thing that you are most pulled towards. Even if it’s not directly beneficial to your job today, at the worst you’ll feel much better finally having scratched that itch.
Read, with a goal: Determine 2-3 skills you most want to develop (strategy? execution? leadership?), pick a set of books and articles that speak to these skills, and work through them. Here’s a set of curated articles and books I previously put together for each of the primary PM skills. I’m happy to share more if you let me know what skills you’d like to focus on. Be careful adding too many items to your list, or book/articles that you aren’t excited about, because you’ll quickly get bored or overwhelmed, and lose motivation.
Read, without a goal: Not all things need to be goal-oriented. Make time to read stuff you’re super excited about even if it’s only tangentially related. Biographies, history books, and documentaries are great for this. As an example of this in action, here’s the story about how Walt Disney’s biography changed Airbnb’s strategy.
Write: One of the main reasons I’ve started writing is because it helps me learn. Consider doing some writing, reflecting both on what you’ve learned over the past 18 months, and on the reading that you’re doing on your time off. This can be as simple as a bullet list of PM learnings, or as in-depth as a Medium article.
Take experiential classes: At a high level, product management, as a skillset, is a combination of leadership + business thinking + product design. Instead of reading about these skills, find some local classes that will help you build them in a different context. Want to work on leadership — maybe take a class on teaching an adventure sport. Want to work on business thinking — maybe take a class on running a local business. Want to work on product design — maybe take a class making pottery. Use this opportunity to look beyond the digital world.
That’s it for this week!
Inspirations for the week ahead
Read: Which Way Do You Run? by Ben Horowitz — “Almost all CEOs know where the problems are, but only the truly elite ones run towards the fear.” 💪
Watch: Optical grape sorting 😳
If you’re finding value here, please share this newsletter with your friends.
And if you’d like some advice yourself, or just want to say hi, just reply to this email. I’ll tackle three reader questions each week (keeping your name and company anonymous) until you quit sending me questions. I definitely won’t have all of the answers, but hey, it’s free 🤷♂️