Bruno Pedro
@brunopedro.com
Building an API Product: Design, implement, release, and maintain API products that meet user needs: https://a.co/d/dE6pQpK
Thanks! A podcast sounds like an interesting idea.
January 18, 2026 at 3:47 PM
Thanks! A podcast sounds like an interesting idea.
Finally, the third ramification is what users get from using your API.
Benefit: the gain that users feel after they use the API you're designing.
A benefit translates directly into a selling proposition that you can use to promote the API and also into a capability.
Benefit: the gain that users feel after they use the API you're designing.
A benefit translates directly into a selling proposition that you can use to promote the API and also into a capability.
January 13, 2026 at 2:56 PM
Finally, the third ramification is what users get from using your API.
Benefit: the gain that users feel after they use the API you're designing.
A benefit translates directly into a selling proposition that you can use to promote the API and also into a capability.
Benefit: the gain that users feel after they use the API you're designing.
A benefit translates directly into a selling proposition that you can use to promote the API and also into a capability.
The second ramification has to do with what users are trying to achieve.
Problem: the difficulty users have that makes them want to use the API you're designing.
A problem can directly translate into a feature that solves it.
Problem: the difficulty users have that makes them want to use the API you're designing.
A problem can directly translate into a feature that solves it.
January 13, 2026 at 2:56 PM
The second ramification has to do with what users are trying to achieve.
Problem: the difficulty users have that makes them want to use the API you're designing.
A problem can directly translate into a feature that solves it.
Problem: the difficulty users have that makes them want to use the API you're designing.
A problem can directly translate into a feature that solves it.
This is the first ramification after you identify a user story.
Location: what tools users will consume the API from, e.g., command prompt, some workflow system like n8n or Zapier, or an LLM.
Location is important because it lets you identify the API style.
Location: what tools users will consume the API from, e.g., command prompt, some workflow system like n8n or Zapier, or an LLM.
Location is important because it lets you identify the API style.
January 13, 2026 at 2:56 PM
This is the first ramification after you identify a user story.
Location: what tools users will consume the API from, e.g., command prompt, some workflow system like n8n or Zapier, or an LLM.
Location is important because it lets you identify the API style.
Location: what tools users will consume the API from, e.g., command prompt, some workflow system like n8n or Zapier, or an LLM.
Location is important because it lets you identify the API style.