Documenting how an APIAPI A set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information. works is easy. Documenting what you can do with it is the hard part, and it's the part that actually matters.
Every PM should have an angle - a specific area of depth that makes them genuinely useful. I think of these as the 5Ds:
You’re probably used to the ever-present idea of an MVP:
Create a product with the minimum set of features that are enough to satisfy early adopters and provide a basis for feedback and future development.
As a product manager, making decisions is a big part of the job. While we all want to make the right decision every time, sometimes things don't go as planned. It can be tempting to try to stick with a decision, even when it's not working, but I've learned that it's better to be able to reverse course and make a new decision.
A foundational part of product management, often overlooked, is understanding the difference between toys, tools, and products.
More random images from 2022.
A small plea: stop abbreviating field and method names in your APIsAPI A set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information., SDKsSDK A collection of software development tools, libraries, documentation, code samples, and guides that help developers create applications for a specific platform or framework., and config.
A solitary gull
arced over stone,
mimicked
by a white vessel
far above and away
which could not flap its wings.