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
What do you do when your team is working their socks off and yet they are getting little credit for the work being done, mainly because the team isn’t able to set concrete expectations with the stakeholder? This obviously reflected as a failure to deliver on part of the engineeringteam. THE CHALLENGE. THE CAUSE.
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.
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.
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?
Last week, I shared that we often get asked, Do API teams need to do discovery ? 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.
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!)
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.
These might be end-user-facing or internal ones like a software platform, for instance; they might directly generate revenue or support commercial offerings. Part of this process should be regular portfolio strategy reviews. What’s more, it might cause poor alignment and weak buy-in.
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).
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.
“ Assume you have new feature requests from business, but your technical team wants to fix the technical debts first, what do you do?”. The conflict between launching new features versus improving the code quality is real and never ending. these are the debts created because of the mistakes the product team makes.
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 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 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.
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.
Listen to the audio version of this article: [link] The Core Product Team Product teams come in different shapes and sizes. But all product teams I have seen consisted of the person in charge of the product—the product manager or Scrum product owner —and developmentteam 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.
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.
Product trios are cross-functional product teams who are responsible for both deciding what to build and then building it. How can you get your engineer to participate in your product trio? What about the other people on the team who aren’t part of the product trio? Do product teams really work this way?
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]
Userpilots key features include: No-code Chrome extension for building in-app flows. In fact, it was first created as an analytics tool, and only in recent years has it also developed an engagement suite. According to user review platforms, their plans start at $7,000/year. Userpilot is perfect for non-technical teams.
As VP of Product at Amplitude, I get the opportunity to work with hundreds of different products teams every year?—?ranging ranging from startups with only a handful of engineers to large enterprises with thousands of PMs. Good product team, bad product team Click To Tweet. PM, Design and Engineering?—?are
When one learns to code, the initial steps involve a great deal of experimentation with code writing and debugging. The learning process usually starts by writing the program and then finding all the software bugs and fixing them. It is a cyclic process consisting of two major steps: Coding and Fixing.
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. When issues arise, customer support teams receive a surge in tickets.
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.
I’ve noticed a frequent executive-level misalignment of expectations across a range of software/tech companies, particularly in B2B/Enterprise companies and where Sales/Marketing is geographically far away from Engineering/Product Management. Let’s call it the softwaredevelopment deli counter problem.
Organizations are developing robust data science capabilities, adding the role of “data scientist” to their ranks. Software can make recommendations to the end-consumer. You have to consider edge cases and problems that might occur if the software makes a bad recommendation or data is missing.
Fallacy #1: ‘Agile’ Equals More Bang for the Buck If you ask founders and managers of startups why they want to become an agile organization, they typically name reasons such as: Becoming more efficient in software delivery, Delivering faster, Improving the predictability of software deliveries. There seems to be a belief?
The most illustrative example of this point relates to software testing. my manager came to me and asked to train a group of manual testers to update them to QA automation engineers. My main purpose was to walk the manual QA testing team through Java basics so that they could continue with QA automation engineer tutor.
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 my reviewers for the Modern Management Made Easy books asked a fascinating question: I've never seen this many women in management or in senior leadership positions. Yes, the Computer Science curriculum had several required Hardware Engineering classes. The idea of a codereview or a design review?
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
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.
Its a behavioral red flag that reveals user frustration caused by poor UX issues that might otherwise go unnoticed. Over time, that frustration robs you of one users loyalty and ripples through word of mouth, online reviews, and social media discussions. Update your teams about unexpected software bugs with Session Replays.
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.
It’s even harder when product managers and engineers are bogged down with work that distracts them from their highest leverage activities of identifying problems and building products people want to use to solve those problems. At its core, product operations enables product teams to achieve better outcomes. What Is Product Operations?
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.
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. So does that mean there’s already localization software on the market that uses machine translation?
What it is: Asana is a versatile task management solution that allows you to manage both personal and team projects. What it does well: With a slogan like “Teamwork without email,” Asana is just that, a good collaboration tool for your team that is intended to reduce the number of back and forth emails about what needs to be done and when.
One of the challenges we've long acknowledged in the tech industry is how difficult the transition can be from a softwareengineer 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.
When you design and build a product, it is important that you regularly demo completed work with the team and key stakeholders. In Agile softwaredevelopment, so-called sprint demos are a key part of every iteration, but whatever product you’re building, be it an app, a website (or even a physical product), demos can be incredibly valuable.
Thanks to a combination of advancements in hardware and software, an outpouring of investment, and a massive spike in business and consumer interest, we believe that virtual reality has hit an inflection point that will propel us from the mobile era to the virtual reality/ augmented reality era. Building non-gaming VR experiences.
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