As part of building the overall project scope a technical author will first need to lay out the justification documentation. This document which can also be considered a “business case” lays out the fundamental reasons for implementing the project. Here’s a simple guide on creating a project justification.
State the Problem
Businesses don’t carry out projects for fun; they perform them in order to solve a specific issue or issues. You need to describe the problem clearly and accurately at the start of your document so that you can then present the solution to that problem.
For example if you intend to implement a new HRMS (Human Resource Management System) your problem may be; “The HR team currently spends nearly 80% of its time on non-productive administrative tasks, reducing the effectiveness of the function dramatically.”
State the Solution
This should be a simple statement to define your project. This enables your reader to understand what it is you’re proposing.
“We intend to implement an automated HRMS system to reduce manual administration by half.”
Supply Supporting Information
The problem and solution aren’t going to justify your project to the stakeholders and decision makers, so you need to provide the right level of information to enable them to support your recommendation.
Examples of the kind of information you should use:
Writing a business case or project justification is an essential part of the larger project scoping process. Ideally you should write this early in the lifecycle of your project to help you obtain funding and support. You will also then be able to clearly identify the objectives of your task so that team members have a clear message to take away.