Agile Product Management, Marketing, and More
Posts tagged simplicity
Internal systems
Aug 30th
One of the takeaways I’m finding in Bill Jensen’s book Simplicity is a reaction to the effect that information overload has on company productivity. As there is more and more information to process to do one’s job, it becomes ever more important for a company to provide tools that not only provide access to information, but which help interpret the information in the sense of analytics. So how does this manifest for a large company aiming to produce streamlined products for the marketplace, that will address (and solve well) a specific problem?
As a product manager with a multinational corporation, I find that (at least at my company in my specific division/subsidiary) there’s a contrast between the streamlined solutions we’re being asked to produce, and the cumbersome internal systems we use to collect and analyze the information we use to design such products. The systems we’re building are “push,” but the systems we use internally are “pull.” Some of this may be due to our company’s implementation of off-the-shelf requirements management and project management tools, but the net result is that the company does not make it easier to easily understand the decisions we need to make, much less make them.
I suspect we are not nearly the only ones.
One of the products I’m developing now is a service which can run client-server or on the web, in order to maximize the base of customers to whom we can provide a solution. I’m finding that questions about–and design of–the internal management components to be used by company support representatives are getting short-changed due to the pressure to meet release targets. This is certainly not unique to this one product, and the support angle hasn’t been ignored, but at the same time the support team’s “use cases” have not been considered with nearly as much diligence and interaction design as the product itself. So in one sense, the sub-optimal experience product managers have with requirements tools is being propagated to the experience support reps will have with service management.
Something I need to reiterate within my organization.
Simplicity
Aug 23rd
I started reading a book about Simplicity titled Simplicity: The New competitive Advantage by Bill Jensen, and immediately one of the author’s assertions struck a chord. One of the book’s hypotheses (simplified) is that knowledge workers spend too much time figuring out what to do, leading primarily to diminished productivity and frustration. For large companies, much of this is laid at the feet of upper management, who may craft a concise strategy at the top but fail to disseminate that strategy appropriately within the organization.
In the case of product companies, whose effectiveness is related to how well they can develop new products and bring them to market, this is one function of product management. Product managers are responsible with becoming intimately familiar with the market’s needs in order to identify opportunities to build solutions the market will pay for, and documenting those problems and needs as requirements. (as opposed to building something we think is cool, and then struggling to find buyers)
With this role as market spokesperson, the product manager guides designers to craft a solution that will satisfy the needs so completely that buyers will be lining up to pay. In some organizations, the product manager serves as the designer as well. Either way, when that design is delivered to development, the vision, goals and solution must be clear enough that the developers can craft an accurate plan and execute without getting mired in confusion and endless analysis paralysis. Certainly the feasibility of the design must be validated before the project team is ankle-deep, but much of the programmer-as-knowledge-worker’s confusion can be alleviated by a clear vision of the solution.
Note: Modern design patterns tell us the product should also be simple and focused, but that is a topic for another post.
Jensen cites his research to assert that the 4 primary causes of confusion among knowledge workers are:
- lack of integration of change
- unclear goals and objectives
- ineffective communication
- knowledge management experience
Certainly the integration of change is a big problem during merger and acquisition activity, forcing disparate systems to be blended. Knowledge management is the problem of finding knowledge already present within the organization. But the other two–unclear goals and ineffective communication–can be addressed within a software development organization by product management.