The Product Strategy Process (Part 2)
The podcast episode explores product strategy involving Shockoe's experts, focusing on mobile application development. The discussion emphasizes working closely with clients, adapting strategies, and the significance of cross-functional team collaboration.
This story was produced through MarketScale. See how Software & Technology teams put it to work with Executive Thought Leadership.
Key takeaways
Product development strategies should adapt to client needs through close collaboration.
Cross-functional team collaboration ensures that development, design, and strategy processes are well-coordinated.
Client feedback is crucial in informing and refining product strategies.
Free workspace
Turn your Software & Technology expertise into content.
Record interviews, organize footage, and write with AI on a free trial of the MarketScale platform for qualifying companies. No demo required, no credit card.
In part two of a series on analyzing and building actionable tips for developing mobile applications, platforms and digital or mobile experiences, Host Daniel J. Litwin welcomed back Shockoe industry experts Chandler Tyler and Mason Brown, both product strategists, and Toz Grewal, a product analyst. The group dove deep into the company’s strategies and how other companies can adapt and apply them as well.
The panel stressed the importance of working with clients for solutions. “We get to work very closely with people both at Shockoe and with our clients to really gain different perspectives on what product development means for different roles,” said Tyler.
Brown added, “I think one of the biggest upsides of us and the entire shop is that our software process is pretty transparent when you’re working with us.”
“People want to feel heard,” commented Grewal. “The client feedback and the client response is a persistent aspect of what informs everything that we do… I think is kind of a foundational of how we approach that problem.”
They also spoke to the importance of having a cross-functional team, where the process is not handed off from department to department but is a collaborative situation.
For instance, Brown and Tyler described how the product strategy team works with clients to pinpoint important aspects of a project in the development stage, sometimes even working with clients on site for a hands-on approach. Grewal agreed, further pushing the importance of teamwork.
“Nothing happens in a vacuum. Strategy doesn’t happen in a vacuum; design does not happen in a vacuum, and development does not happen in a vacuum,” Grewal added. “So, similarly, those three efforts function in their best possible form when they’re done in tandem with the client and in tandem with each other.”
Litwin will be back with the panel for the third and final installment of the product strategy process on the “Haptic Feedback” podcast.
Your experts belong here
Every story in MarketScale Software & Technology starts with a company putting its solutions engineers, product teams, and customer engineers on the record. Buyers are already reading this topic. The only question is whose experts they find.
Buyers ask AI engines who to consider, and published expert answers are what those engines cite.
About the author
Daniel Litwin is a journalist of multiple disciplines focused on finding and telling engaging stories for B2B communities. He has interviewed executives from Fortune 500 companies including Honeywell, Microsoft, John Deere, and Chipotle, and leads editorial direction at MarketScale. Litwin hosts weekly shows and podcasts while helping develop new content approaches across the MarketScale platform. He holds a B.J. in Radio/Television Reporting/Anchoring and a B.A. in Spanish from the University of Missouri-Columbia.
