CVSankars Designs Limited



Boundary setting in eLearning Projects


Written by: Candice V. Sankarsingh
Senior Learning Quality, Evaluation & Instructional Technology Advisor

, , , ,
  1. Scope Creep: Every small concession—whether a “quick fix” or an additional feature—accumulates over time, often without corresponding compensation. Projects grow beyond the initial agreement, leading to missed deadlines and overwhelmed teams.
  2. Loss of Profitability: When managers aim to please by saying “yes” to out-of-scope tasks, they fail to recognize that every additional feature or revision costs time and money. Without a proper change request or additional invoicing, the company’s profitability is compromised.
  3. Client Misunderstandings: Always saying “yes” sets a dangerous precedent. Clients may believe they can get unlimited changes for the initial price, leading them to undervalue the manager’s and team’s expertise. This creates confusion about what’s included in the original agreement.
  4. Burnout and De-motivation: Employees often end up suffering from the consequences of people-pleasing. They become burned out by the need to complete unplanned tasks under pressure, and morale drops when they feel that their efforts aren’t valued or protected by management.

Managers must adopt firm but respectful language when communicating with clients. The following statements can help maintain professional boundaries:

Several project management tools and techniques can be employed to ensure that clients receive exactly what they pay for—and nothing more unless it’s properly accounted for. These include:

Change requests are an essential part of managing scope. When a client requests an alteration, enhancement, or addition, this triggers the change request process. Here’s how it typically works:

  1. Identification: The client or project team identifies a need for a change. This could be adding a new feature, extending the timeline, or adjusting the budget.
  2. Documentation: The change request is documented using a formal change request form. This form outlines what is being requested, the reason for the change, and the potential impact on the project.
  3. Impact Assessment: The project manager and team assess the impact of the change on the project’s scope, timeline, and cost. This analysis is presented to the client.
  4. Approval: The client must formally approve the change, acknowledging that it may result in additional costs or a longer timeline. Without this approval, the change is not implemented.
  5. Implementation and Billing: Once approved, the change is implemented, and an invoice reflecting the additional work is sent to the client. This ensures that the company is compensated for any extra effort.

When clients try to overstep and dictate what should be included in the project without considering the boundaries, it’s crucial to maintain control. One effective method is to be proactive in invoicing for additional work. Here’s how to approach this:

A management style that focuses on constantly pleasing clients may seem beneficial in the short term, but it is ultimately counterproductive. Setting proper boundaries, adhering to project scope, and using tools like SOWs and change requests can help protect the integrity of the project. Managers need to remember that they are partners in the project—not subordinates to clients. By confidently setting and enforcing boundaries, they can ensure that clients get what they pay for, while also maintaining profitability and preventing toxic work environments.

, , , ,

Enter your email below to receive updates.

Discover more from CVSankars Designs Limited

Subscribe now to keep reading and get access to the full archive.

Continue reading

Discover more from CVSankars Designs Limited

Subscribe now to keep reading and get access to the full archive.

Continue reading