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?
In this edition of Productside Stories , we dig into Brians 30-year legacy of building, integrating, and supercharging product portfolios across healthcare, software, media, and government. The pivot to customer list acquisition worked out eventually, but only because they discovered the real story during diligence, not after.
How product managers can adapt core responsibilities across different organizations and contexts Watch on YouTube TLDR Through his research and practical experience at MasterCard, Nishant Parikh identified 19 key activities that define the role of software product managers. Why study the 19 key activities of software product managers?
Think of Net Promoter Score (NPS) software as a tool to measure your customers’ feelings about your product, and categorize them based on their level of loyalty (promoters, neutrals, and detractors). Plus, the ability to create custom NPS dashboards allow you to analyze the results easily without writing a line of code.
Be Clear on What a Software Platform Is. Different people have suggested different definitions for the term software platform. Let me briefly share mine: I view such a platform as a collection of software assets that are used by several products, as the following picture illustrates. But platforms come with potential drawbacks.
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.
Kevin has almost a decade of experience working at some of the world’s most innovative software companies. 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.
Alert fatigue is a common problem among engineering teams that handle operations and maintain infrastructure. The result is lots of semi-meaningful alerts, noise, context-switching, and multitasking for the on-call engineer. We introduced regular alert review sessions for teams dealing with frequent alerts.
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.
We’d like to share some insights from what we’ve learned so far about software delivery and operations over the past few weeks of working from home during COVID-19 , and how we as an engineering team have adjusted to this unprecedented, unpredictable situation. New situation, new processes? What do we need to change?
We had just hired a new VP of Product who was radically (and rapidly) changing our product development process, and our engineers – based remotely, in Argentina – were struggling to keep up. “To Well, before, product knew what was going on and engineering didn’t.” and one engineer in Iceland. And what can I do about it?
When engineers encounter friction when learning a new API, it reduces their likelihood of having success with your product. APIs, once implemented, have incredible lock-inbecause it takes engineering resources to switch products, customers are much more likely to stick around. But more often than not, its due to the curse of knowledge.
For much more hands-on learning, sign up for Colin’s live four-week cohort-based course on AI prototyping , where you’ll master AI prototyping tools, debug common issues, and build a fundamental understanding of how coding works. Use code “LENNYSLIST” to get $100 off. Enrollment closes January 23rd.
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.
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. Share the work.
The conflict between launching new features versus improving the code quality is real and never ending. And sometime during the sprint, the development team realizes that if we want to implement it the correct way - ensuring engineering best practices, it will overspill and is not feasible to complete in the earlier planned timelines.’
Software development with sustainability in mind is a rising trend in digital spaces. While software is intangible and doesn’t directly consume energy or produce emissions, its environmental implications lie in its development and usage. As software builders, we are uniquely positioned to influence this environmental trajectory.
One of the main examples of this are the customized software applications that companies are rushing to develop to allow them to better connect with their users. To create such solutions, companies need softwareengineering professionals who can provide the expertise required. Let’s dive right in. by the year 2024.
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. As a softwareengineer, no matter how senior you are, you always seek codereviews before deploying new code to production. .
This sort of hand-waving has been most prevalent in software companies, where the supposed price of strategy missteps is seen as low. 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.
One practice that both companies established was weekly executive-level metrics reviews. I've come to believe that establishing such a metrics review meeting is critical for developing an effective data-driven culture and I wanted to share some of the best practices around doing so. Why metrics reviews matter.
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. I’ve yet to come across a software leader who isn’t. I’ve yet to come across a software leader who isn’t.
Its written to help non-engineers understand the value of softwareengineering. Its chock-full of stories about how the author solved business problems by writing code. Even though it had been ten years since I had written a line of code, I decided to dive back in and I started automating my business logic.
However, I didn’t receive any particular instructions except for one: I should familiarize the group with Java basics and then later transfer them to the QA automation engineer mentor as soon as possible. Well, I’d never worked with testers or rather I’d never taught testers how to code. Who is a QA Automation engineer?
It breathes life into your engineering team, and teams across the company, as customer issues and requests are resolved quickly and efficiently. Production is the only place where your code, infrastructure, and customers come together to represent objective reality. Here at Intercom, we believe in shipping as quickly as possible. .
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. Don’t add to your stack unless you’re certain that your use case will not be satisfied by existing software. The top ten technical strategies to avoid.
Right off the bat, Kristen acknowledges that the freemium model isn’t a universal cheat code for winning sales. The beauty of the freemium model in an enterprise setting is that the supplier duediligence process is already much further along. Listen to the full episode above or check out Kristen’s key takeaways below.
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.
The team had been working for almost a year and had a huge amount of code under their belts. But just because it was a lot of code doesn’t mean it worked. The relationship between QA and Engineering was bordering on food fights, and we’d only achieved half of our requirements. We’d made great code. How did I get here?
Continuous improvement is a continual process to improve components of enterprise software?—?processes, Regardless of today’s software development aspect, increasing demand for new features in the products makes competitive advantage higher than ever. Changes can be large or small, which depends on the software projects.
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. Second Attempt.
In a fastmoving digital economy, many organizations leverage outsourced software product development to accelerate innovation, control costs, and tap into global expertise. Table of Contents What Is Outsourced Software Product Development? What Is Outsourced Software Product Development?
On one hand, everybody expected me to focus on the problems that will help them to succeed in their workflows or function, and on the other hand, I had limited time to give all the problems their due attention it. He completed his MBA from UNC Kenan-Flagler (USA) and Engineering in Computer Science from BIT Mesra, India.
At Intercom, we aim to run less software. This allows us to develop teams of deep domain experts to support and enable product engineers as they build the next generation of Intercom, and provide world class observability tooling, scaling, reliability, and secure-by-default build patterns. . a customer-facing error) by default.
He translates complex business problems into solutions that are easily consumed by engineering, marketing and sales. Jordan has enterprise Software-as-a-Service experience within the facilities management, legal and pharmaceutical verticals, having most recently worked at ServiceChannel, Epiq Systems and Medidata Solutions.
And while machine translation is often suited to live conversations due to the importance of responding in real-time, anything less than human translation for knowledge base articles and onboarding flows won’t make for a good customer experience – and will inevitably result in low engagement and adoption rates.
He translates complex business problems into solutions that are easily consumed by engineering, marketing and sales. Jordan has enterprise Software-as-a-Service experience within the facilities management, legal and pharmaceutical verticals, having most recently worked at ServiceChannel, Epiq Systems and Medidata Solutions.
Chi started sitting in on quarterly business reviews with top vendors. These were review sessions Chis companys account management team was already having, and they gave her the chance to ask vendors about their order volume. Chi worked with engineers to build the vendor-facing API and shared the timeline with VPs.
Software bugs are a budget killer for your company and a buzzkill for your users. Even with a rigorous software testing process, one pesky bug always slips through. In 2014, a software error on Amazon caused some items to drop to just one penny. Engineering teams are pulled away from planned projects to investigate.
Our product engineers are empowered to build great features, fast. A large part of making this belief a reality is the idea of running less software. So we decided to do something contrary to our engineering principles – run our search infrastructure ourselves on Elastic Compute Cloud hosts, or EC2 as it’s known.
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? Answer RFPs – mostly the product sections.
Review design. As I’ll explain below, the “why” and “where” form your product vision, and your product team (especially your engineers), not only want this from you, but need it in order to do their best work. Why does product vision matter to your engineers? Write code. Review sprint work in retro. Write spec.
Product management doesn’t run Engineering; Engineering runs Engineering. And at least in public, Engineering and Product leadership need to be shoulder-to-shoulder , actively supporting each other at every turn. But there are some engineering team configurations that I see as problematic. So
How product mangers can improve collaboration in cross-functional teams Today we are talking with Maziar Adl, the co-founder and CTO of Gocious, an organization that creates product roadmap management software. Many of the tools product managers use on a day-to-day basis are engineering-focused ticketing systems.
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