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
Without input from a product manager, a designer, and an engineer, it’s difficult for us to account for the cross-functional perspectives we need to build successful products. However, most companies tend to have more engineers than product managers or designers. Which engineers should participate in trios?
From surfacing hidden landmines during duediligence to bringing entire product orgs under one cohesive vision, Brians got the battle scarsand the winsto prove it. Below, well unpack his real-world advice on making acquisitions work, retaining your best people, and aligning tech stacks for a post-merger world that actually innovates.
Drawing from his 20+ years of technology experience and extensive research, Nishant shared insights about how these activities vary across different organizational contexts – from startups to enterprises, B2B to B2C, and Agile to Waterfall environments.
Assume you have new feature requests from business, but your technical team wants to fix the technical debts first, what do you do?”. Before we get to the approach, lets look at the two different types of Technical debts that may come your way. The ‘Deliberate Tech Debts’ Imagine a scenario?—?‘You Copyright?—?Dilbert.com
As an innovative concept, Developer Experience (DX) has gained significant attention in the tech industry, and emphasizes engineers’ efficiency and satisfaction during the product development process.
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. So when it comes to building your technical strategy, you need to assess each component in relation to what success will look like for your business.
Relative to other standard roles defined in an organization such as Ops, Marketing, Tech etc., Often, this is due to resource constraints rather than a lack of understanding of a PM role. This includes Tech estimates (at least T-shirt sizing) and resources identified for the projects. Hard Skills Required for the Role.
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.
Challenges due to hypergrowth. Onboarding: A huge number of hirings, from C-Level to PMs and Tech lead Process-oriented, not mission, not goals Purpose lost: make new employees impact the team as soon as possible No feedback-loop with new employees. Regarding continuous delivery: Very technical focus (e.g.
It’s a familiar problem for all companies that scale fast – how do you keep your core technologies manageable for the increasing number of teams that depend on them? This surfaced as an increasingly large percentage of our product teams’ time being spent on operations or deep diving into understanding our small set of core technologies.
FullStory – Best for product, engineering, and marketing teams – Custom pricing (free trial available). LogRocket – Best for developers and engineers – Free plan available; paid plans start at $69/month. Sentry – Suitable for engineering teams – Free plan available; paid plans start at $26/month.
A startup development team consisting of a product manager and two offshore engineers was facing major challenges in meeting client deliverable deadlines – repeatedly. Each major release deadline created a high pressure environment with engineers working overtime in the weeks prior in order to meet delivery dates. THE CHALLENGE.
But in today’s fast-paced world, your customer support can only be as effective as the technology that underpins it. Study after study shows that the vast majority of support teams are unhappy with their current customer support tech stacks. Download The Ultimate Modern Support Tech Stack guide. Is your tech stack ready?
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.
Here’s how the two approaches differ: Aspect Traditional MBOs OKRs Compensation Link Directly tied to bonuses Deliberately separated from compensation Goal Structure Combined goals and metrics Separated objectives from measurable results Review Cycle Usually annual More frequent (e.g.,
Shift from fixed yearly planning to rolling quarterly reviews to allow flexibility in roadmap decisions. Run structured stakeholder sessions to ensure leadership, engineering, and marketing teams remain aligned. Translate technical details into user-friendly language using real-world analogies.
When you reach senior level on an engineering track, you’re expected to be optimal in your hard skill set. Despite not having a formal education in engineering, Sarah landed a job as a developer in the French consultant Grand Manitou. Then, four years ago, in 2018, she got a job at Algolia as a software engineer.
In my company, we review a living document with our management chain on a quarterly basis to align business direction for the short-term (immediate one to two quarters) to the long-term (two to five years). The challenge to the product managers is to translate these into a more functional plan for our engineering team. First Attempt.
And while seeing this work come to fruition, Sam, a Product Engineer at Intercom, was inspired to find more ways to get involved. As she tells it, “When I was fresh out of college, I was working at my first job in the tech industry. Think about the impact that racism has already had in tech. Know the scope of the issue.
Engineers are often reluctant to participate in discovery. This is only natural: Through years of bad habits, many of us have shown engineers that we only value them for the code they can write. But there are many reasons why engineers are one of the essential members of the product trio. And this is a good thing.
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.
When running brainstorming sessions, Ellen found that engineers in particular were quick to jump to feasibility concerns. The back-end platform already supported the ability for direct messaging, so there was very little technical feasibility we had to worry about—the interface and user experience were the main challenges.”
Step 1: Preparation (3-5 weeks) The preparation step is a foundational effort where a lot of the groundwork and duediligence is done to inform the strategy selection process. These illustrative concepts are not intended to be “shovel-ready” for engineering to build on. This could include the founders, CEO, etc.
Next, the analytics setup depends on engineers, which disrupts their workflow. It also draws out the process by requiring time-consuming agreement on needs and strict protocols, like QA reviews. Often due to analysis paralysis , overwhelming amounts of information, or a lack of clear insights that drive product decisions.
It is tailored for product teams who need to send NPS surveys inside their app and analyze it without technical expertise. 3 Delighted for e-commerce, tech, and non-profit teams Creating NPS surveys with Delighted. So they make it easier to send these surveys and get more responses.
But when we make technical decisions, we like to be conservative. In practice, being technically conservative looks like reusing existing technologies and frameworks in our stack, or promoting tried and tested patterns and solutions. Here, Waheed discusses our engineering principle “Be technically conservative”.
He is convinced that product is the single most important success driver for tech companies, which is why he founded Prodify to share what he learned from being an advisor to over 50 tech companies to realize their full potential. Ben has led successful technology products for the last 25 years. He
For example, while Teresa recommends creating a product trio that includes a product manager, engineering lead, and a designer, she acknowledges that some product trios might be made up of slightly different members. It’s not about finding the right tech stack; it’s about finding the tech stack that works for your team.
He translates complex business problems into solutions that are easily consumed by engineering, marketing and sales. Paul is an experienced product management professional with over 15 years of experience in technology management and 10 years in product management. She majored in Industrial Relations in her undergraduate degree.
He translates complex business problems into solutions that are easily consumed by engineering, marketing and sales. Paul is an experienced product management professional with over 15 years of experience in technology management and 10 years in product management. She majored in Industrial Relations in her undergraduate degree.
Feasibility risk impacts the capacity of the team to build the product given time, skills and technology constraints. The sales team and leadership promised the clients to deliver the product without having any discussion with the engineering team. Resource, technology and poor planning impact a product’s functionality.
The relationship between QA and Engineering was bordering on food fights, and we’d only achieved half of our requirements. As we were getting closer to the end of the year, my senior vice president called me in, to review our progress against our goals. I’m not a technical Product Manager. In fact, our tests regularly failed.
It’s always better when we’re together Photo by henry perks on Unsplash When I entered the wondrous world of product & engineering for the first time, I did not understand why there was a split between Product & Engineering. Engineering decides how and executes. One cannot exist without the other.
We provided consulting, insurance brokerage, information technology and business process outsourcing services. This was due to incorrect contribution amounts, the system not finding an account, or invalid employer data. She has co-facilitated and led Agile training sessions for students in Master of Engineering in Silicon Valley.
You also might be reading this post thinking: “Who’s adding new tools to their tech stack right now?” Incorporating these tools into your customer experience tech stack will drive more engagement, gather high-quality customer feedback, and help inform your product roadmap. Supporting tech. This is a valid question. Rightpoint.
Instead, they hand off work from team to team—the back-end engineers design the data model and system architecture, the front-end engineers build the interface elements, the mobile engineers work toward feature parity, etc. These teams can rarely deliver value on their own. Click the image to see a larger version.
The career paths for sales engineers (SEs) and solution consultants (SCs) are wide open due to the blend of business and technical skills, sales skills and positioning expertise required to succeed in this role. Are Sales Engineers and Solution Consultants the Same? Are Sales Engineers and Solution Consultants the Same?
As Kristen says: She predicts that this strategy of letting the product guide the sales process is the future of tech: “I think that’s where a lot of the future of sales and tech in general is going to go to some extent, which is to really let the product guide the people. Crowning the customer.
We discuss the benefits of low-fidelity prototyping, the engineering design process, and how to use prototypes effectively to solve problems and validate ideas. In the OEDK, students have access to high-tech equipment, but they won’t always have the OEDK available to them.
Consequently, a platform should have its own product strategy and roadmap , KPIs , product backlog , and well-designed software architecture that leverages the right technologies. Ensure that the Platform is User-Led, Not Technology-Driven. Treat the Platform as a Product.
The SpaceX Raptor engines are a great example. They have gotten significantly simpler iteration over iteration despite being rocket engines for space travel. We were now reviewing the features to be sunset, and the teams to work on them. It was a big and risky commitment, as no one likes to work on ‘clean-up’ duty.
Innovation is the economic engine for organizations and a key source of new value. Here are key criteria to consider: Strategic fit with company objectives Sales potential and market size Competitive landscape User experience and customer value Technical feasibility and complexity Financial metrics (e.g.,
Here are some of the questions they’ll discuss: What’s the relationship between design, development, engineering, and product and your company? How deep does your understanding of the technology go as a PM? How do you manage executive expectations, customer expectations, and technical resources? Christy: All right.
Laura Tacho is the CTO at DX , has taught over 1,000 tech leaders through her course on developer productivity metrics , and on the side is an executive coach for engineering leaders. Unfortunately, if yours is like most companies, your product and engineering teams disagree about what “moving faster” means.
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