Vibes are not requirements.
This process enumerates the functional and business-oriented requirements that are required to make your project a success. It is a crucial step in proper execution of a website or web application project. This is important whether you're replacing and expanding upon existing digital tool, or envisioning an all-new digital system implementation.
This type of task results in a high-value artifact — business requirements documentation — that can be referred to at all stages of your project, from design and exploration through implementation and testing. This process often creates greater alignment between stakeholders, spurs important discussion and clarification, and provides definition of what the system needs to do and offer to be a success. It helps answer the questions of "What will this system do for us?" and "What won't it do?", which are important to expectation-setting and planning of future processes and resource allocation.
AI is making it easier and easier to create and deploy new digital systems. I apply BA and Requirements Gathering to help define those new systems, making sure they include the right features and account for the real, human user needs. This can also create actionable user statements, stories, and instructions / prompts for AI-based coding systems as well as test plans.
Feature Summary
A narrative report describing project context, intended functionality, in and out of scope details, and other factors to support upcoming implementation work.
Project Brief
A text-based report describing processes, observations, learnings, recommendations, and anticipated functionality required for the client's website.
Project Brief
A comprehensive text-based document that captures key details about the project's genesis and background, enumerating key problems to solve, current strengths and opportunities, prioritized audiences and anticipated features.
Send me a message to tell me about your project and how I can help.