Standardizing API strategy is about consistency, not trends.

Here’s how my work on API design and governance has been continuously cited in official public-sector API technical guidance:

“Defining API personas is a crucial step in designing and developing APIs (Pedro 2023). API personas help programs understand the needs, preferences, and behaviors of target users and consumers. Personas ensure developers are creating APIs that meet their specific requirements and testing and validating API functionality across each persona’s use cases."—Office of Systems Engineering and Architecture, “API Technical Guidance” (U.S. Department of Defense, MVCR-2 (PDF), April 2025, p. 54, Section 8.2.2; U.S. Department of War, MVCR-3 (PDF), March 2026, p. 58, Section 8.2.2)

The cited work is the “Build a Successful API by Understanding User Personas” article, from May 2023. In that piece I say that “APIs explicitly designed for targeted users are more likely to be adopted.”

Excerpt from the U.S. Department of War API Technical Guidance citing my work. According to the API Technical Guidance some techniques to identify and define API personas include conducting user research, analyzing usage data, identifying user roles, creating user journey maps, prioritizing personas, and developing persona profiles.

To me, being consistent means putting in the work every day and following your beliefs. It’s about playing the long game instead of following the latest trends. Sooner or later, you’ll see your work helping others create something bigger than what you thought was possible.