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
For example, my first iteration focused on the problem statements, targeted customer, technical strategies, pricing strategies, and competitiveness evaluation, which was all excellent content that offered important product context but just not the right place. First Attempt. As expected, I ran into a lot of issues at the start of the process.
To understand the problem with technical debt roadmaps, we’ll start with a quote from renowned philosopher, Homer Simpson. It’ll go away ,” the famous TV dad advised his family on dealing with challenges. In this article, we’ll discuss why technical debt roadmaps don’t work. We call it a mistake.
Summary: A ProductTank London talk that advises you accept that you are part of any failure that happens and be specific about the issues that you face. Put simply, this inability to work through personal problems together means that you’ll never be able to come up with solutions for more technical issues. How can we move forward?”
I would recommend this model if you have no technical or product management background. For major brainstorming, problem-solving or strategic planning I would advise that you again meet in-person and work out the general strategy you’re heading. Constructive negative feedback on tasks and goals is welcome.
Examples include your stories, and your requirements for your Technical teams. The intent of your Six-pager is always to cover the “Why” and to some extent the “What” but never the “How” Cut the clutter A six-pager is not the first document I advise you to start thinking with. ConstructsConstructs are one abstraction level above UX.
Communication Write thoughtful, well-structured business cases; considering strategies and objectives Analyze and distill complex information Question and challenge in constructive ways; present ideas confidently and respectfully. The only requirement is that you must be legally able to work in Canada. When: Flexible start date.
Communication Write thoughtful, well-structured business cases; considering strategies and objectives Analyze and distill complex information Question and challenge in constructive ways; present ideas confidently and respectfully. The only requirement is that you must be legally able to work in Canada. When: Flexible start date.
Communication Write thoughtful, well-structured business cases; considering strategies and objectives Analyze and distill complex information Question and challenge in constructive ways; present ideas confidently and respectfully. The only requirement is that you must be legally able to work in Canada. When: Flexible start date.
Communication Write thoughtful, well-structured business cases; considering strategies and objectives Analyze and distill complex information Question and challenge in constructive ways; present ideas confidently and respectfully. The only requirement is that you must be legally able to work in Canada. When: Flexible start date.
Others were consultative, or they advised about technical needs. If the CS team was advanced enough, CS Ops were building out onboarding procedures, enabling support with better motions, and constructing customer-facing teams, such as renewals, while keeping them aligned.
The questions are in various categories and are inclusive of: General Questions Technical Questions Organization and Time Management Questions Feedback Questions Conflict Resolution Questions Product Management Process Questions Career Path Questions Management and Leadership Questions Let’s dive right in. What is your greatest weakness?
Effective Roadmap Planning and Development Process for Enterprise Products
AUGUST 2, 2018
It’s very important to have a very clear definition of these persona constructs to the most precise form. I typically advise the below format. Define the MVP use cases, put together the functional and technical design, carry out POC and evaluate the product viability. Theme Goals (KPI) H1 H2 Sales Revenue 1. Development a.
How do you manage executive expectations, customer expectations, and technical resources? I’ve been kind of actively running away from management roles, and mostly that’s just a factor of the things that I really wanna learn or I just really wanna learn how to be a really, like, kick-ass technical PM. So that’s me.
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