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
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). What systems/metrics/processes do we need to measure and track winning?
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. As I strive towards becoming a product leader, I wanted to understand the best practises in product management and in the process develop my own product philosophy. .
When an organization shifts from delivery or feature teams to product teams , the first step is often a change to team structure. Delivery and feature teams are often structured by function—front-end teams, back-end teams, mobile teams, etc. These teams can rarely deliver value on their own.
When speaking with founders and CEOs, we often hear concerns like this: My project manager is losing confidence in the developmentteam. I think that poor communication and differing team cultures might be part of the problem, but how can I know for sure? This is where a technical review can be useful!)
From the creators of DORA, SPACE, and DevEx, and in collaboration with Laura Tacho and the team at DX , I’m excited to introduce you to Core 4. Laura and her team spend every working hour researching, designing, and experimenting with ways to measure and improve team velocity (while avoiding burnout).
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.
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.’
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 engineeringteam configurations that I see as problematic. So
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 engineeringteam.
“If you think good design is expensive, you should look at the cost of bad design,” Ralf Speth, a former Jaguar Land Rover CEO. The study by the Design Management Institute analyzed the performance of design-led organizations that place influential design decisions at the top as compared to the Standard & Poor’s index over 10 years.
Before founding Viable, he held senior leadership roles in engineering, technology, and product. Often somebody on the team is responsible for reading through all that stuff, synthesizing it into insights, and disseminating those insights across the team. This is a very manual process, so few teams decide to do the work. [4:22]
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? They likely don’t have all the answers.
As noted in my last post , Sales and Marketing often wonder whether Engineering is sufficiently motivated and engaged. Motivation and engagement look different on the tech side of the room: the outbound team often can’t tell whether Engineering is emotionally engaged. Some Engineeringteams are unmotivated, though.
In our early days, like many other companies, we prioritized the speed of shipping over maintaining the consistency and interconnectedness of our system. We knew we had to change tack and find a way to align teams and functions as we scaled. Alongside this issue, we were quietly building another type of debt: functional debt.
It’s too bad I didn’t have first principles to draw on at the time. Identify Base Principles — What are the fundamental truths of product development? Tesla’s Roadmap and Lessons from First Principles Historically, car manufacturing has been dominated by internal combustion engine (ICE) vehicles. Trust, outcomes, value?
It defines, communicates, supports, and improves important operations which can be standardized, such as communication, planning processes, team gatherings, and training. How it’s become a critical function for scaling effective product teams. Developing and maintaining a continuing education program for product managers.
Product teams often fall into the trap of spending most of their time on the core functionality of the products they’re building. Without an accessible onboarding process , customers may never reach the stage where they can use the game-changing features your team has worked so hard to build, making outcomes difficult to achieve.
One of the challenges we've long acknowledged in the tech industry is how difficult the transition can be from a software engineer to an engineering manager due to the vast distinction in the skill set to be great at the new role. Doing this right means a lot more than simply supporting your team. a product leader.
Some people want to believe that they won’t happen or don’t want to talk about them so that they don’t risk being seen as bad at their job. I’ve never seen a roadmap naming the bugs a team wants to introduce?—?but The Institute of Electrical and Electronics Engineers, the IEEE , is the body responsible for standards in software.
Organizations are developing robust data science capabilities, adding the role of “data scientist” to their ranks. You have to consider edge cases and problems that might occur if the software makes a bad recommendation or data is missing. Engineeringteams tend to understand a lot about the application and who is using it.
If you’re a fan of the kanban system , this will become your go-to method of organization. What it is: Asana is a versatile task management solution that allows you to manage both personal and team projects. How to Use it: You can create projects and tasks within the projects, assign tasks to teammates and track progress.
Three years later I became a web application engineer at a startup that built software for military and private industries. I became director of communications, leading the development of intranets and web applications. Designers vs Developers The work culture in this large organization was unlike anything I’d ever experienced.
8 AI trends that will define product development By Greg Sterndale Posted in Digital Transformation , Product Published on: February 12, 2025 Last update: February 10, 2025 From modular architecture to agentic AI How product development will evolve in 2025 & beyond In product development, change is the only constant.
Three years later I became a web application engineer at a startup that built software for military and private industries. I became director of communications, leading the development of intranets and web applications. Designers vs Developers. Tension between designers and developers was palpable.
Here’s our story how we’re developing a product using machine learning and neural networks to boost translation and localization Artificial intelligence and its applications are one of the most sensational topics in the IT field. If so, what is the value of the solution you’re developing? Often people confuse it with automation.
This led me to reach out to 14 leading Product Managers and talk with them about how they use customer feedback in their own companies and teams. It’s a two-level processing system: Do we know “Who” is giving us this feedback and why? A further step into this is to actually be part of those teams sometimes.
As we look at what it takes to develop non-gaming VR products, their separation from gaming becomes very important. Developing business products in VR, however, is like creating a new sport by combining American Football and what the rest of the world calls Football. So what does all of this mean for product development?
And this is why we decided to bring you a special episode about these latest developments in the world of AI, what they mean, and whether it’s time to apply it in real-life scenarios such as customer support. OpenAI released their most recent machine learning system, AI system, and they released it very publicly, and it was ChatGPT.
In developing live streaming digital solutions for years, we’ve collected quite a massive of valuable insights, industry challenges, app feature trends, and development key points that will help you pave the way to building a demanded high-quality streaming platform. Its market share is projected to reach $534.37
I try to help product and sales teams succeed under the mantra “Easy to Sell, Easy to Renew.” Yet most of the product community’s dialogue centers around the relationship with product and engineering. I’ve struggled to find many examples detailing how to bond product and sales teams ( Antonia Bozhkova offers a good perspective ).
As up and coming engineers in Silicon Valley, Jean Hsu and Edmond Lau long sought more influence and impact in their respective positions – but they couldn’t shake the feeling of being stuck. Many engineers feel like they must make a jump into management to lead. Jean: Especially with engineeringteams.
” GTM leaders typically ascribe this situation to lack of attention, poor work ethic, or weak understanding of customers on the part of product management – i.e. personal failures best addressed by replacing or upgrading product staff. Or That slashes the work to <600 hours/week/product manager.
Secondly, as great product managers are also great capacity builders for their teams, you should start looking for opportunities that AI can present for your product. Spam engines are the most famous example here but there is much more. An ML system would probably catch more mistakes but would be far more expensive to build.
Some product teams are moving away from written PRDs to visual artifacts like mockups and prototypes. Eric Ries, in his post “What is customer development? Some product teams will use written methods across both the problem identification and solution definition steps, while others will use visual methods. Written Methods.
While every product team I've worked with leverages customer feedback to inform product decisions in some way, most fall short of designing their customer feedback loop to maximize the benefits to the product team of gathering, recording, and synthesizing feedback. Catalog Your Sources of Feedback.
Negative user experience = lost customers Users get frustrated when they encounter functional bugs like a payment system failure, a broken feature, or a poorly functioning app. Wasted time on bug reproduction and fixes The software development process is lengthy. When issues arise, customer support teams receive a surge in tickets.
If something bad happens locally, like an office losing power, having a copy of important data somewhere else isn’t enough. You’re not an engineer. On a typical day, Grone meets with leaders of the support team, works with developers and answers questions from individual salespeople. We’re Here for the Symphony .
Building effective teams with people from different disciplines can be challenging due to various circumstances. It’s about gathering together professionals from different functions such as engineering, business, design, marketing, legal, and others. It’s not just about bringing together a diverse team. Myth #2.
Everywhere I go, I see massive amounts of product waste : development work delivered on time/on budget that doesn’t drive sales or customer satisfaction or business improvement. Yet Yet somehow we don’t see this waste, or mis-attribute it to engineering process problems. features. Commitments
Stacks can be developed at the project, team, or functional level and are regularly used to improve internal collaboration, measure the impact of marketing activities and reach customers in new ways. Without this foundation, your marketing stack can become a set of siloed tools that will bog your team down in complexity.
This year I developed a new reading approach, in which I read several books in parallel, usually from different topics. Strategy is visible as coordinated action imposed on a system. It is an exercise in centralized power used to overcome the natural workings of a system. When I say the strategy is “imposed,” I mean just that.
Most of us have been through the results of poor management of bugs: hair-on-fire, last-minute late nights to madly scrambling to critical fix bugs blocking a release, or stopping a customer from using a product. Does your organisation provide you and your team with direct access to customers, or are there gatekeepers?
They go from planning one product to the next, foregoing the opportunity to establish fundamental product instincts, which only develop after managing the same product for an extended period of time. Or as Belsky puts it, “to hack their reward system”. They never unlearned being self-centric. They never learned to be customer-centric.
Nova is Amplitude’s in-house columnar-based storage & analytics engine. Nova’s original design is inspired by a few exciting systems like PowerDrill , SCUBA , Trill , and Druid. to 8s over the last year due to high volume queries. As we were analyzing the performance of our systems, we had a few discoveries.
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