Boomi API Persona Development
Categories: UX Design
Responsibilities: Design, Interview
Talk to APIM end users during 1-hour interviews to identify and understand their behaviors, attitudes, needs, and goals.
Summarize that information with personas that represent significant segments of the people who use APIM to enable effective product decisions
Planning/Research
Identifying our users.
- Identify potential personas
- Draft personas based on user interview findings
- Finalize personas based on APIM stakeholder feedback
User Interviews
We interviewed both our internal staff and current platform users about their experience with API Management, and pursued three different personas based on this information. The API Admin, API Architect, and the API Developer.
“I think when you’re trying to build an API Gateway, you have to have some level of network understanding. A person with no networking knowledge is really, really, really going to struggle in that area.” – Software Developer III
“When you look at these screens, there’s a lot of stuff in here. Where do you even begin? There’s just so many options, and there’s so many things all at the same time that I just had no clue where to begin. And it was sort of overwhelming to me.” – Sr. Systems Engineer
Common Pain Points
- Users say it’s hard to figure out where to get started and what each next step is.
- Boomi’s documentation is limited, although new architecture diagrams have recently been added.
- Even with a background in integration, networking, and infrastructure, it took users multiple days or more to figure out.
- Setting up a API Gateway is a cross-disciplinary effort, particularly in the Enterprise (Infrastructure, Networking, Data Security, Boomi Systems Admin, DevOps).
Design
Once we identified common usage, needs, goals, and pain points we consolidated these into easily scannable cards, and shared them with the product teams and began to design all features based on these three personas.
