This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Productside | Product Management Courses & Training Breaking the Silos: How Product and Engineering Build Better Together In Season 3 of Productside Stories , we sat down with Guy Gershoni , Head of Engineering at genesIT, for a candid conversation on what it really takes to build great products in todays complex tech environments.
Adding delight and emotion to your application can have a profoundly positive impact on the user experience, create ‘tweetable moments’ and turn customers into evangelists. Do you celebrate with them when they’ve hit an important milestone?
He emphasized the importance of role clarity and how the lack of it often leads to frustrated product managers leaving their positions. Its success relies heavily on the thoroughness of the preceding market research phase while setting the stage for subsequent product positioning and vision development.
As VP of Operations, Kim worked with third-party engineering consultants to improve the platform’s ROI and customer outcomes. Whether you’re coming from engineering, business operations, or another field entirely, your unique background can provide valuable perspective and skills for a successful product management career.
Speaker: Robert Webber, Author and Innovation Leader
Agile was a grassroots engineering movement that caught most software leaders unprepared. Management was never taught how to establish the positive and supportive environment necessary to motivate self-directed teams, resulting in disappointing Agile transitions.
Are you inviting your engineers to participate in discovery with you? Does your organization prefer that your engineers only write code? Marty Cagan , in Inspired , argues, “If you’re just using your engineers to code, you’re only getting about half their value.” And, sadly, many engineers make this mistake themselves.
It’s no secret that engineers can be hesitant to participate in product trios. We’ll hear from several members of the product team at Ramsey Solutions about their not-so-smooth transition to working in product trios, especially when it came to getting engineers to participate.
In some cases, the CPO may also be responsible for product development and engineering. Level up with a 501 Advanced Portfolio Management Course from Product Management University, a course crafted for product managers looking to advance into leadership positions. How Lucrative is a Career in Product Management?
Think your customers will pay more for data visualizations in your application? Five years ago they may have. But today, dashboards and visualizations have become table stakes. Discover which features will differentiate your application and maximize the ROI of your embedded analytics. Brought to you by Logi Analytics.
Strengthening Relationships Through Gratitude Product managers work closely with engineers, designers, and various other stakeholders. This simple act of appreciation not only boosted morale but also strengthened the engineer’s commitment to future projects, resulting in a more collaborative and engaged team.
For the very first time, we’re releasing Engineer Chats , an internal podcast here at Intercom about all things engineering. Previously hosted by Jamie Osler , a Senior Product Engineer at Intercom for over seven years, it’s now up to Principal Systems Engineer Brian Scanlan to pick up the baton and keep the chats going.
Key results should be measurable outcomes that tells the team whether they are making positive progress, like “200 people sign up for the demo after reading the blog post.” How could your team use cross-functional OKRs to improve collaboration between product, engineering, and other departments?
A risk is an uncertain event that may have both a positive or negative impact on a product. The sales team and leadership promised the clients to deliver the product without having any discussion with the engineering team. The product and the engineering team did not get the opportunity to conduct a feasibility study.
For this edition of Product in Practice, were not talking with a product manager, a designer, a UX researcher, or even an engineer. They came up with the outcome Passioneers are engaged and positive and clear on their role and responsibilities based on the feedback survey and quiz related to Continuous Discovery Habits. But not today.
You could start with using DACI as a baseline: develop ways to quickly identify / guess at their DACI profile and how your DACI profile and theirs can interact positively. Form a high-level understanding of the alignment in your relationship (positive, negative, or neutral). Test See how that initial test works in the actual meeting.
Previously, he spent nearly eight years at Palantir, working as a forward-deployed engineer. Removing hierarchical titles (making everyone “forward-deployed engineers”) reduced internal competition and politics, forcing recognition based on merit and impact rather than position. Where to find Nabeel S.
Recently, at Hemnet, Sweden’s beloved property platform, she led product development that drove a 130% increase in top line revenues, making it the growth engine of the business. Leadership doesn’t always mean management Many professionals enter product management from technical backgrounds, such as engineering or development.
Or does your product manager write requirements, your designer designs, and your engineers code? A product trio is typically comprised of a product manager, a designer, and a software engineer. A product trio is typically comprised of a product manager, a designer, and a software engineer. What’s a product trio? Tweet This.
how AI is getting closer to replacing PMs , which parts of the job are most likely to be impacted ), so I wanted to take this week to share an important message: I believe that product managers are the best -positioned role in tech to thrive in a world of AI. In fact, many jobs will start to look more like product management. Read more
Use data to support your position and explain the trade-offs. Engineering may want to focus on technical debt, while marketing wants to accelerate a product launch. Suggested Solution : The key is to respectfully push back when necessary. As a PM, you’re often stuck in the middle, tasked with balancing both needs.
This year, it’s estimated that approximately one in four people have quit their jobs , and those positions are remaining open for much longer than expected. I’ve led teams of engineers for almost a decade but when I look back at my own management career I regularly thought I was a “good manager”, at times even a great one.
Your job as a product manager is to make sure designers and engineers have crystal clear targets for customer value they can easily hit. Once you start writing functional specs and working with engineering to orchestrate sprints, put a fork in yourself. It’s just not the responsibility of a product manager. Here’s the honest truth.
Not every company has seen all these changes, but by and large I think it's been a positive push forward and I'm proud of where we've come from and where we have gotten to. -- 2014: "I do not need Product Managers, I can run my company myself,I have the strategy." We've come a long way but we still have far to go.
How many more engineers do you need to do everything on the backlog? If you have four times as many engineers, you’ll be able to go four times as fast, right? . Stakeholders wanted everything on the backlog, and “Prioritization” discussions would always turn into resource discussions.
Brought to you by: • Explo —Embed customer-facing analytics in your product • Dovetail —The customer insights hub for product teams — Archie Abrams is the VP of Product and Head of Growth at Shopify, where he leads a 600+ person growth org across product, design, engineering, data, ops, and growth marketing.
New software engineers quickly learn that a lot of complexity arises from error handling. It’s hard to balance investment optimally across ML, product, engineering, and design. What was the cost of a false positive going to be? You might easily be over-engineering your solution or solving slightly the wrong problem.
In a traditional company, a product manager sits in the middle between business stakeholders and the engineering team. The product manager gathers requirements, documents them, a designer creates a design based on those requirements, and the engineers build software based on those requirements. Tweet This. We don’t want that.
It seems like some areas of risk clearly map to members of the trio—engineers should be responsible for feasibility, designers should be responsible for usability—but other types of risk don’t match up with a particular role. Yes, engineering is going to contribute more to feasibility and product managers might contribute more to viability.
Hence it is critical that one is aware of the best practises of the role and develops his own philosophy which results into maximum positive leverage for the organization. The PRD is a PM’s primary communication tool with engineers. Scaling the team: As you scale the engineering team, it takes effort to onboard the new team members.
The relationship between QA and Engineering was bordering on food fights, and we’d only achieved half of our requirements. I knew that I couldn’t look into the code to see that our engineers had built what I was looking for. We would regularly meet to discuss the features required, what the customers expected. Similar, right?
He translates complex business problems into solutions that are easily consumed by engineering, marketing and sales. In this position, Dustin’s primary responsibilities include product portfolio management, new product introduction and product line strategy deployment. Ari Tiktin Mobile & Emerging Media Product Director, CNBC.
And while seeing this work come to fruition, Sam, a Product Engineer at Intercom, was inspired to find more ways to get involved. My team’s lead engineer stopped what he was doing and announced to the all-male room, ‘Looks like the token female engineer has arrived.’ Know the scope of the issue.
However, this is a naïve analysis that overlooks lost market share due to poor strategic thinking, or the demoralizing effect on engineers having to repeatedly rewrite code because of poor product-market fit. consulting engineer, helping customers implement Chef’s products. operations engineer across a wide variety of industries.
The proposal was: Have the developers write their own end to end tests, put the QA people in a position where they build the infrastructure for that to be possible and then start measuring. Our QA engineer quit. We lost the QA Engineer, as we couldn’t to fix all of the issues with the process. He was not happy.e
Many people, especially engineers, might try to fix this by making the elevator faster. Look for positive exceptions of someone else dealing with the problem or a time when you solved the problem before. Positioning and the words you choose are very important. I like the Slow Elevator Problem. Rethink your goal.
He translates complex business problems into solutions that are easily consumed by engineering, marketing and sales. In this position, Dustin’s primary responsibilities include product portfolio management, new product introduction and product line strategy deployment. Ari Tiktin Mobile & Emerging Media Product Director, CNBC.
As it turns out, he’s also quite the writer – since the last time we spoke , he has published not one but two books on engineering. After writing An Elegant Puzzle about the challenges of engineering management in high-growth organizations, his focus shifted to a career path that’s much less understood – the technical leadership track.
Our support reps will routinely run through the logic behind product decisions with our engineers and product managers. Instead, you should remain personal and look for a positive way to say no. Having that line of communication means we can say no with the right level of detail. Don’t change your tone of voice.
During this journey, some of the key challenges that I faced are follows: I found it very difficult to define the positioning statement for the product. For example, in one of the features, engineering leadership wanted me to cut down on the scope to accommodate the ask within the expected timeline. More About The Product Mentor.
Camille was previously the CTO of Rent the Runway, VP of Technology at Goldman Sachs, Head of Platform Engineering at Two Sigma, and Global Head of Engineering and Architecture at JPMorgan Chase. She is about to release new newest book, Platform Engineering: A Guide for Technical, Product, and People Leaders.
Its goals describe the user and customer benefits the entire portfolio should create and the positive business impact it should achieve. First, the GO Portfolio Roadmap is built on outcomesits an outcome-based, goal-oriented plan. They are its most essential element. Any feature shown on the roadmap must help meet the corresponding outcome.
From premature optimization to over-engineering solutions for your product, it’s easy to get caught up in making technology decisions that slow you down instead of speeding you up. These things are usually artifacts of some engineer’s Objectives and Key Results (OKRs). The top ten technical strategies to avoid.
These quantitative methods allow product managers to make data-driven decisions about product features, pricing, and market positioning. Engineers and product developers often focus on the technical aspects of a product, but customers are mainly interested in what they get out of it.
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content