You start with a fully-formed, marvelous idea for the product to solve your problem. This then gets reviewed to confirm its awesomeness and gets added to the product plan or backlog. From epics to stories to specifications to implementation, your idea gets transformed into one or more product features and is released to everyone, ready to solve the problem you had... two-to-three years ago.
Except that's not quite how it happens.
lives projects and other products.
For depressing inspiration on the relative importance of ideas, see Idea Guy Bill Gross's Ted Talk (hint: the idea is only part of the success equation).
As a product manager, I'm now part of a familiar process of prioritizing what we build without being too concerned with how it's built.
What I didn't tell you back as a functional consultant, the reason you liked (or didn't like) my functional designs was because of you, my dear technical consultant. I found a match between what the customer wanted and what you would likely implement.
Though technical formats should not dictate a proper content model, architectural and technical constraints actually help a design (see Design of Design, a nice follow-up Brooks' Mythical Man Month). In past business analysis roles I worked with developers and business owners to convert marketing and business owner wants into system needs.
Now I'm one of the "business owners." But my focus is still on helping the customer and their content editors.
Except that's not quite how it happens.
Lots of Familiar Ideas
In enterprise (possibly any) software development, the ideas are plentiful, evolving, and fleeting. Suggestions repeat and even compete with each other. Anamnesis reigns, where no idea is really new, just a recollections from pastFor depressing inspiration on the relative importance of ideas, see Idea Guy Bill Gross's Ted Talk (hint: the idea is only part of the success equation).
As a product manager, I'm now part of a familiar process of prioritizing what we build without being too concerned with how it's built.
What I didn't tell you back as a functional consultant, the reason you liked (or didn't like) my functional designs was because of you, my dear technical consultant. I found a match between what the customer wanted and what you would likely implement.
- You liked automation and the Event System? Sure, it's part of the design toolkit.
- Content Delivery pro? Perfect, let's go dynamic with "widgets." Editor configures the Component, you deliver the results with a few Content Delivery API calls.
- Container components are your thing? Sure, we'll go modular but not dynamic just yet.
I helped discover the WHAT; you figured the best HOW.
Now I'm one of the "business owners." But my focus is still on helping the customer and their content editors.
Tags:
December 24, 2015 at 11:48PM
Open in Evernote
No comments:
Post a Comment