Suggestions
David Lifson
Chief Product Officer at Buoy Health
David Lifson is a marketplaces specialist with a proven track record of building exceptional teams that deliver impactful results. He holds an M.Eng in Computer Science and a B.A in Computer Science from Cornell University. David Lifson has an extensive professional background, having served in leadership roles at reputable organizations such as Buoy Health, The Knot Worldwide, XO Group Inc., Homepolish, Poppin, General Assembly, Postling.com (acquired by LocalVox Media), Etsy, and Amazon.com. His experiences range from Chief Product Officer to various VP and Director positions, showcasing his expertise in product management, marketplaces, and team building.
Highlights
Software used to do nothing until we made it do something. Now, AI products built on LLMs will, from Day 1, answer anything we ask, albeit with unknown quality, accuracy, and safety.
This poses some really challenging design questions. We’ve always thought in terms of funnels: we lead users down a path via navigation, wizards, and CTAs, hopefully resulting in conversion events that generate revenue or helping the user accomplish a Job To Be Done.
What is the UX analogue in an AI world, where the entry points to a “funnel” are as infinite as human language can invent?
This is the Amazon Alexa problem: people didn’t know what they could use it for, so they memorized a handful of incantations that work (clock/timer/alarm, weather, music, re-ordering stuff) and stopped there.*
This is also the Tesla everything-hidden-behind-a-flatscreen problem: sometimes you just want to turn the AC down and the volume up. Physical buttons and knobs are great at this, and hiding these features behind layers of navigational touchscreens might look cooler but is objectively worse UX.*
I don’t know exactly what good looks like yet, but my hunch is that AI products should present a UX that is opinionated about how we want the user to use us, without limiting the user if they have other ideas. More guideposts and guardrails than fenced in funnels.
Lots of user research and playing with prototypes awaits; excited to share it with you all as we figure this stuff out.
—————— *If you’re interested in reading the footnotes as well as my work-in-progress thoughts (today: the increasing value of brand and community now that Google has AI Overview answers in search results), sign up for my free newsletter: https://lnkd.in/g44P3_rB
My wife, Karla, starts grad school today.* Yesterday, her school held a matriculation ceremony, welcoming the new students and kicking off the school year. It got me thinking about tradition, history, and ritual markers.
Product Managers are change agents; built into our bones is a drive to change ‘what is’ into ‘what could be’.*
And, because of who we are, it’s easy for us to underestimate the value of tradition, the value of celebrating what came before, the value of taking a beat to mark a milestone.
The thing to remember is that, for many, change is quite hard. It might be easier for the PMs, designers, or engineers who is creating the future, just like how you’re less likely to get carsick when you’re the one driving. But, for most of the team, all this change is happening around them, and the only times they really hear about it are at company all hands meetings.*
Tradition, history, and markers can help with that feeling. We can use it as a cultural structure that creates stability amidst the swirl.
By reminding ourselves of what has come before, how we navigated it, and how we survived it, we can replace fear with confidence in the face of the next challenge. And by demarcating when one period ends and the next begins, we help everyone digest what was and join in the pursuit of what’s next.*
- Honor the past before pivoting to the future.
It offers closure that respects what was. Then, do a big kickoff of the new initiative.
- Celebrate every major launch with a memento.
I remember my first day walking into Amazon in 2006 and seeing laminated launch posters up on the walls, autographed by each member of the team that built it.
- Do retros.
Create a safe space for people to share what was frustrating and annoying. Unpack the lessons learned and process the feelings. Agile / scrum teams have been doing this for 20 years, and I’d encourage others to try it, too, at your next offsite or all hands.
- Create an oral tradition.
“Do you remember when…” stories are great, not only to help new folks know the history, but because they often represent formative moments in the company culture.
“Change management” is often talked about as procedural, something to be program managed. And it is. But it’s also cultural, psychological, and emotional.
—————— *If you’re interested in reading the footnotes as well as my work-in-progress thoughts (today: what made Michelle Obama’s speech so great?), sign up for my free newsletter: https://lnkd.in/g44P3_rB
