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?
Understanding OKRs: From Intel to Modern Product Teams The evolution of Objectives and Key Results (OKRs) began at Intel during the 1970s and 1980s, where Andy Grove transformed the traditional Management by Objectives (MBO) system into something more dynamic and outcome-focused.
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.
On call work like this can be a powerful customer orientated activity that connects engineers to the value customers get from your product. The quality of our alarms and on call procedures were inconsistent across teams and we were using ad hoc review processes for new and existing alarms. What we learned.
Often, this is due to resource constraints rather than a lack of understanding of a PM role. Data PM: organizations dealing in data products (building AI/ML based products) prefer a PM with data science background so that they can appreciate the problems well and being able to work with data engineers/scientists.
I discovered that I must research and understand the entire system and process, problem solve with my team, and share lessons learned. This was due to incorrect contribution amounts, the system not finding an account, or invalid employer data. These system errors increased our backlog and costs, and delayed enrollments.
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 SystemsEngineer Brian Scanlan to pick up the baton and keep the chats going.
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.”.
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.
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.
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.
It breathes life into your engineering team, and teams across the company, as customer issues and requests are resolved quickly and efficiently. We encourage engineers to ship the smallest thing (we call them cupcakes ) as quickly as possible, and every new hire on our engineering team ships a feature within their first week.
Product engineers are experts at identifying, understanding and solving problems. Yes, the code that you write and the systems that you build are major contributing factors to the success and growth of a business. Here are the five areas that we encourage product engineers to contribute to as they seek to maximize their impact.
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.
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.
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.
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. Her background is in developer tools and distributed systems. For more, check out her LinkedIn and her blog. That’s what product velocity enables.
This mostly worked, but it required a lot of administrative work to keep our systems in sync. There were dozens more that required that we make changes in all of our systems. Its written to help non-engineers understand the value of software engineering. Some of these challenges were due to me being a beginner.
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.
The answer is to engage a trusted outside source for a Technical Review – a deep-dive assessment that provides a C-suite perspective. At TechEmpower, we’ve conducted more than 50 technical reviews for companies of all sizes, industries, and technical stacks. A technical review can answer that crucial question.
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.
Today, our systems dynamically scale to serve about 50,000 web requests per second at peak, 26,000 background jobs per second, and 11,000 public API requests per second – demonstrating our ability to continuously scale to meet the requirements of modern enterprises. You need to store multiple millions of user records. Can Intercom do that?
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. What systems/metrics/processes do we need to measure and track winning? Where do we play? And where do we not play?
by Rich Archbold, Senior Director of Engineering at Intercom. 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. The same is true in software.
This fragmentation occurs when critical business information becomes scattered across disconnected systems, creating dangerous blind spots for product managers trying to make informed decisions. Now you must dig through support tickets, DM your engineer, and finally ask your data analyst to run a custom query. Sound familiar?
As a result, you’ll find no shortage of articles telling you how to write a review – or as they’re commonly known, a post mortem – of your incident. In the past, we asked a set of five questions during incident reviews at Intercom: Do we know what happened? What could our systems do better? Focus on the details.
Our product engineers are empowered to build great features, fast. It underpins a whole host of core Intercom features – Inbox Views , API , Articles , the user list, Reporting , Resolution Bot , and our internal logging systems. In Intercom, we believe that shipping is our company’s heartbeat. persistent": {.
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. In fact, our tests regularly failed. A production release was a distant vision.
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?
That could be a simple pass-fail scoring or a more complex system. [8:21] The level of complexity of the portfolio management system needs to line up with the decision-making pace of the organization. In some cases, a simpler system is better than a complex system. 8:21] Who is involved in portfolio management?
We discuss the benefits of low-fidelity prototyping, the engineering design process, and how to use prototypes effectively to solve problems and validate ideas. The episode also covers potential pitfalls in prototyping and best practices for product managers.
To get more projects done, you need to optimize the workflow of your system. Just because the system can handle more work doesn’t mean that more work will promote the best flow of work. The value proposition of a product or project initiative may be sensitive to a specific due date. 14:31] Execute projects more reliably.
Systemic Thinking: The Key to an Impactful UX Strategy Systems Thinking is a holistic approach to problem analysis and solving that emphasizes viewing systems as a whole, rather than focusing only on individual parts. What is Systems Thinking? Interrelationship: all parts affect each other within a system.
Customers are mostly flexible with their car preferences due to the nature of the marketplace. Enter CarFYAI, CarFY AI is an AI-powered system for streamlining car discovery in Car-as-a-Service platforms, providing a personalized and enhanced user experience for customers. Image credit: Karena E.I Its simple and straight to thepoint.
IDEs) that help you write code with the help of AI Let’s review the most popular tools in each category to see what they can do and what we can build. Claude goes one step beyond ChatGPT’s abilities with their Artifact system. GitHub Copliot , Cursor , Windsurf , Zed ): Development environments (i.e. Unbelievable.
Now that the COVID pandemic is over, travel management systems are valuable because business travel is back on the table. Consequently, travel software development companies come up with a solution called travel management system. What is a travel management system?
The engineering team works on progressing the product but doesn’t communicate information back up to product management or executive groups. When I was the director of engineering, I often saw that what I understood the product to be was different from how directions of other departments in the organization understood the product.
Amid this incessant search for perfection, two paradigms have become prominent: Test-driven development (TDD) and feature flag-driven development (FFDD). Test-driven development (TDD), a software development approach in which tests are written before the code, is akin to building a safety net before performing a daring tightrope act.
He’s an individual contributor (IC) PM who leverages AI tools and a suite of productivity systems to get more done with fewer resources (and management layers). Instead of spending valuable time after the meeting reviewing notes and drafting a summary, do the work in the meeting itself. “Fairness” isn’t coming.
How our core technologies were being used was also diverging, leading to needlessly increased complexity in our systems. The positive impact we had on engineering was readily apparent, which led to more investment in the core technologies area. It also led to a queue of engineers wanting to join the team.
Before founding Viable, he held senior leadership roles in engineering, technology, and product. You pipe your feedback into one system that is your record for customer feedback. Our system produces weekly reports. Before founding Viable, he held senior leadership roles in engineering, technology, and product.
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. If you’re a senior engineer and want to further your career, what skills should you develop? How do people move into staff engineering roles? What’s the right way to do this in your company?
If you’re a pre-sales solution consultant or sales engineer, falling into the trap of telling vs selling can happen before you even know it, even though your intentions are always on the mark to start the demo. You have to reverse-engineer every question back it into a user scenario of the specific job task someone is performing.
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.
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