Personify

A reel presents the contents of your product or experiment to make it easy to share the entire story behind the idea to drive xfn collaboration across your product team. Coming soon!

This has been a summer of change, which is especially true for my startup, Personify. Hey I'm Om, and it's about time I re-introduce myself. I'm a designer turned entrepreneur, and the Co-Founder, CEO of Personify. We're building Personify to help product teams shape insights to ship experiments and share outcomes that drive business and user value. Today, product managers (PMs) belabor requirements documents that come either too late or too early in the process, missing the purpose of the activity entirely in order to speed up producing an output. Even worse, a feature or experiment that ought to be defined as a team is formed and presented unilaterally disenfranchising partners to simply deliver their outputs by arbitrary deadlines. The burden of sharing the plan, the progress, and deciphering the impact falls on product leaders to share organically. With everything else going on, let's just say a lot get's 'lost in the sauce.' Hours and days are lost in rote work like formatting slides for monthly product updates from a lengthy PRD that's sitting in a word document. The information is fragmented across tools making reporting each update a wild goose chase that can last days. This sucks for the PM, the team, and the entire organization. We believe there's a better way. This morning I published our manifesto to share the guiding principles that inspire the experiences we create for our customers. https://lnkd.in/eQPByJvU If this resonates with you, follow along as I share notable updates, learning and progress as we bring our vision to life.

This has been a summer of change, which is especially true for my startup, Personify. Hey I'm Om, and it's about time I re-introduce myself. I'm a designer turned entrepreneur, and the Co-Founder, CEO of Personify. We're building Personify to help product teams shape insights to ship experiments and share outcomes that drive business and user value. Today, product managers (PMs) belabor requirements documents that come either too late or too early in the process, missing the purpose of the activity entirely in order to speed up producing an output. Even worse, a feature or experiment that ought to be defined as a team is formed and presented unilaterally disenfranchising partners to simply deliver their outputs by arbitrary deadlines. The burden of sharing the plan, the progress, and deciphering the impact falls on product leaders to share organically. With everything else going on, let's just say a lot get's 'lost in the sauce.' Hours and days are lost in rote work like formatting slides for monthly product updates from a lengthy PRD that's sitting in a word document. The information is fragmented across tools making reporting each update a wild goose chase that can last days. This sucks for the PM, the team, and the entire organization. We believe there's a better way. This morning I published our manifesto to share the guiding principles that inspire the experiences we create for our customers. https://lnkd.in/eQPByJvU If this resonates with you, follow along as I share notable updates, learning and progress as we bring our vision to life.

Soon you’ll be able to toggle between the problem and solution space seamlessly!

Get clear guidance on what's missing to get your experiment ready for launch! #product #requirements #experiment

Build and grow your metrics library for your organization, one experiment at a time!

Creating a standard and building in process that holds teams accountable to a high bar of quality and thoughtfulness isn't always easy. We're working hard on this front to think about how the tools you use to shape experiments can help nudge and advocate for the right values without sacrificing speed when it comes to new product development.

“A problem well-defined is a problem half solved.” - John Dewey. A thoughtful hypothesis is a framework for meaningful solutions to explore. Reinforce an evidence based process to evaluating the problems and solutions for each product experiment.

Getting clear about scope that's in direct line of sight of the insight and hypothesis help your team get just enough context to design and estimate the effort to build a new experience.

Your product team has more data and tools than ever and yet it's harder than ever to earn clarity you can share to inspire the team with purpose. It's time for that to change.