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
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?
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.
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.
by Rich Archbold, Senior Director of Engineering at Intercom. The same is true in software. In this battle, I’ve found a secret weapon hidden within one of our core engineering strategies, an idea called Run Less Software. When I say “execute”, I don’t simply mean the engineering challenges of building something.
First, I did not know how to frame, develop and present product strategy in a systematic way, and second, as a startup, my company has not historically had a good track record of strategy being developed outside of senior management (read: founder). Two major obstacles stood in my way.
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.
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.
Softwaredevelopment with sustainability in mind is a rising trend in digital spaces. I would like to thank Tremis Skeete, Executive Editor of Product Coalition, for his valuable contributions to this article's research, development, and writing. Let’s explore how and why this matters. It comprises of four components: 1.
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.
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.
Today, Ill be covering the most common usability issues that arise when developers start working with a new API. When engineers encounter friction when learning a new API, it reduces their likelihood of having success with your product. Remember, an API defines a pre-defined language for how code can interact with another service.
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. So, what can one do?
In a recent live stream from one of our mentors of The Product Mentor , Chris Butler, lead a conversation around “Business Development vs. Product Management”. He translates complex business problems into solutions that are easily consumed by engineering, marketing and sales. Vikas started his career as softwaredeveloper with Siemens.
Continuous improvement is a continual process to improve components of enterprise software?—?processes, Regardless of today’s softwaredevelopment 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 a fastmoving digital economy, many organizations leverage outsourced software product development to accelerate innovation, control costs, and tap into global expertise. Rather than building and maintaining a large inhouse team, businesses partner with specialized vendors to handle design, development, testing, and deployment.
Core 4 pulls everything they’ve learned from working with thousands of teams into a single unified developer productivity framework. 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.
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.’
But then, one day, I found myself reading Ask Your Developer by Jeff Lawson and I realized I was the one making the mistake. Dont Ask Humans to Do Tasks That Should Be Automated If you arent familiar with Ask Your Developer, its a great read. Its written to help non-engineers understand the value of softwareengineering.
In today’s competitive business environment, technology is increasingly shaping the strategies that companies develop to try to outdo their competition. 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.
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.’ She published it in our Slack channel with over 200 members.
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.
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.
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?
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
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?
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.
Their team was busy working and coding the product but nothing had been officially released yet. Rahul admits this was due to him not believing that they had product/market fit. The post The Product Market Fit Engine by Rahul Vohra appeared first on Mind the Product. Measuring Product/Market Fit.
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. .
He grows revenue and adoption, and ensures product by turning business problems into profitable, simple, easy-to-use solutions Jordan works closely with his market, executives, and internal subject matter experts to develop roadmaps, and communicate these roadmaps internally and with clients.
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.
He grows revenue and adoption, and ensures product by turning business problems into profitable, simple, easy-to-use solutions Jordan works closely with his market, executives, and internal subject matter experts to develop roadmaps, and communicate these roadmaps internally and with clients.
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.
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. This evolution in understanding reflects broader changes in how modern organizations approach product development.
Many CEOs of software-enabled businesses call us with a similar concern: Are we getting the right results from our software team? We hear them explain that their current softwaredevelopment is expensive, deliveries are rarely on time, and random bugs appear. These are classic inflection points for a development team.
CMU Master of Science in Product Management program student Erick Valencia landed a PM experience of a lifetime as part of a student team developing a driverless race car system to race in the Indy Autonomous Challenge. As a business engineer, just like a Product Manager, you’re trained to perform different key roles in an organization.”.
We discussed the most common challenges developers face when starting with a new API. Its more common for developers to decide what to build. This story stands out because as a PM, Chi used discovery tactics like customer interviewing and story mapping to shape the development of an API.
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. .
Depth over breadth: Revolut’s leaders deliberately go extremely deep into 7 to 10 projects (out of 100 or more running simultaneously), but at a code and technical implementation level. This eliminates the uncertainty of whether poor traction is due to a bad idea or poor execution, making feedback interpretation clearer.
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.
A couple of months ago, we reviewed the new Firefox browser designed for developers. Since then most of our developers kept Google Chrome as their primary browser. With the built-in developer tools, there seems to be no further need for more tools. 16 of the best Google Chrome Extensions for developers.
As a principal engineer, you can effectively be operating as a team of one – and that makes it a little trickier to manage your time. . At Intercom, we believe that a principal engineer should “set goals autonomously and at the level of scope and ambition usually associated with a team.” Engineering org needs. Personal goals.
When I joined Wetu in 2014, I was the 7th employee, we had just over 100 companies using our software, we were exclusively available in Africa, and the product was already 5 years old. Since then we have grown to over 100 employees, we have more than 800 companies using our software, and we have expanded globally.
How can you get your engineer to participate in your product trio? Most product trios are comprised of a product manager, a designer, and an engineer. The most common form of cross-functional collaboration happens between product managers, designers, and engineers. The engineers start building.
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.
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