A BA is accountable for that software solution. So, communicate clearly to ensure that the creator + tester understand expectations.

A user story is a short description of a functionality/goal that will guide a developer or tester into fully understanding a user's goal.

This article explains API specifications, stories, acceptance criteria and UI improvements.

When thinking about APIs, picture the old mobile phones with a speed dial functionality.

It is one thing to learn the BA tools and techniques, but it is another, to apply those tools and techniques appropriately.

Humans communicate with other humans, so computers should communicate with other computers/systems/servers; this is the concept of APIs.

For great user experience, JTBD shouldn't be seen as a rival of Persona, the should be merged into SMART User Stories for Software Dev.