Common Risks Faced

This is a list of risks and examples we face, and can expect to face, throughout the duration of a project.

Definition:  when stakeholders add more deliverables or push back deadlines. This can delay the project timeline, and resource utilization.
Possible solution: We want to be accommodating where possible, but the mistake that often gets made is when small requests are automatically processed and acted upon without any discussion of the added “out of scope” effort or the impact to the timeline. It’s better to over-communicate to the client that we are doing them a favor and taking time out to get something done for free. In addition to these conversations, having a shared “change/request log” spreadsheet or document with the client is another way to make clear that every new request or alteration has real impact and to track the volume of such items throughout the project. This doc can be paired with some kind of policy that is shared with the client along the lines of: “We’ll take care of up to 10 hours of out-of-scope requests throughout the project, but beyond that, we will need to issue a change order for additional scope and budget as well as impact to timeline.” This way, there are clear boundaries set and protections in place against scope creep.

Lack of understanding from client: Client doesn't have clarity on their product.
Lack of understanding from our side: Not asking the proper questions. 

Was this article helpful?
© 2025 LowCode Internal Docs