What's Next?
Once you have your Concept or Concepts, share them with your developers to make sure they make sense and that any points that need clarifying get resolved. Then use a prototype to test the concepts with representative users before committing to the full implementation. Include an ordinary task and a plausible change of plan. Can users explain the objects and relationships, predict an action's effect and revise the result? Testing with Users describes how to record independent success and the help required. Stakeholder agreement is useful, but cannot answer these questions on its own.
Remember, Concepts should only contain things that end users should be aware of. They should not include implementation details.
Once the feature is ready for testing (as the Concept may need refining during the development process), the documentation and QA teams can be given the Concept, this will ensure everyone is using the same terminology, and is aware of the intended use-cases, states and behaviours.