Suggestions
Charles Jessup
Product Manager & Gen AI Enthusiast | MBA | PMP | Facilitator | Oil & Gas | Built 5+ web applications | Certified Professional Scrum Product Owner Level 2 | SAFe Agilist
Charles Jessup is a Senior Product Management Coach at TEKsystems, where he specializes in developing software products and collaborating with teams of designers, developers, and data scientists to build SaaS web applications. His expertise extends to product management and agile coaching, focusing on helping organizations understand and implement effective product strategies.
In addition to his role at TEKsystems, Jessup is active on LinkedIn, sharing insights about product management and industry trends. He engages with the community by discussing topics such as the importance of understanding customer needs when developing features and the latest advancements in AI technologies. His approach emphasizes collaboration and strategic thinking in product development.
Jessup's professional background includes significant experience in product management, where he has earned a reputation for his dedication and ability to work well with diverse teams. He is recognized for his contributions to the field and continues to influence aspiring product managers through his coaching and mentorship efforts.
Highlights
Product managers: When your boss asks you to build a feature, it is your job to understand why they want that feature built. Good product managers will also do some research and suggest alternative solutions that might be better/faster/cheaper.
Screenshot from my copy of “Impact Mapping” by Gojko Adzic.
Just found this cool Jobs-to-be-Done poster and wanted to share.
Story time:
A digital product team I'm working with has struggled with internal adoption of their software (their software is only used by employees).
They started interviewing users to better understand their needs and now we're working on describing it using a Jobs-To-Be-Done framework. It's really fun seeing how their product notes change from things like "users are too busy to use our software" to "users have a specific job to do and our product could help them do it faster".
Next step: Identify user pain points & opportunities, and then design solutions to solve them
