By Mohit “Mo” Sahgal

In the last blog, I introduced the pitfalls of both avoiding initiative work effort estimation, and inaccurate work effort estimation. This blog focuses attention on what happens when you guess or create a high-level, summarized or generalized work effort estimate. The most common examples of guessing and generalization are arbitrary activity duration. An example of that would be saying “in 90-days” or ” in a 9-month” delivery cycle. These unreliable “predictions” ignore the real factors driving the work effort, staffing, task duration and costing. When these factors aren’t working together as a cohesive unit, the organization’s strategy execution could take a hit too, especially if they aren’t using the best software. What is more challenging is guessing without accounting for assumptions and risks. Even when estimation is difficult, guessing should be avoided. If you have a delivery business, you want to show your customers that you are reliable, using a service like the last mile delivery software can help your customers and you keep track of everything being delivered.

The implications of generalization and guessing are self-evident: cost overruns, delays, poor customer satisfaction, poor performance, missed targets, and increased risk. These are aspects of a business that you should work to improve on if you realise the company is not reaching their goals. If we’re talking about improving customer satisfaction, once customers realise that your company holds something as significant as a iso 9001 certificate, this shows them that they are top priority when it comes to your business.

Sometimes, the success of a business is based solely on how many customers they receive in a certain time period. The more customers they have, the more money that they will have coming into the accounts. If your customers aren’t happy with your products or services, they will go through your customer service helpline, and it is important that this effectively works so they are persuaded to return. Some businesses might need extra help to ensure the success of this service, so weighing up the positives and negatives of zendesk vs freshdesk can help to establish which one will be the best tool to help your business and its customer service move in the right direction.

Organizations can avoid thili saisfaiction by using a combination of techniques, some of which may appear to be obvious but are often overlooked:

  1. Clearly defining the scope of the work (“charter”). Key elements required for estimation include: major workstreams, activities, major milestones, interdependencies, resource and skill requirements, etc.
  2. Assessing the impact of changes or exceptions.
  3. Using controls to track changes or exceptions to the charter as formal record of senior management acceptance.
  4. Updating the work effort estimate based on the accepted changes or exceptions.
  5. Creating and updating a detailed work plan to accomplish the stated objectives, regardless of the implementation methodology.
  6. Establishing a baseline for the plan.
  7. Updating the plan with actuals on a regular and frequent basis.
  8. Using earned value to address schedule and cost variances.
  9. Using analogous estimates, subject matter advisor input, and prior project experience to begin the sizing, benchmarking and corroborating the work effort estimate.
  10. Maintaining an effective risk / issue log to communicate any “blockers” which require management attention.

Many of these items appear to be common sense advice, but lack luster results are commonplace. Maintaining good controls is difficult. If it was easy, then every project would be successful and somehow all of the exceptions would be magically addressed.

In next week’s blog, I will explore the implications of point number 5 above – the misalignment of the estimating approach with the delivery methodology; that is, sizing the work effort which does not adequately reflect the work required to achieve the objectives of the initiative.

About the Author:

Mr. Mohit “Mo” Sahgal is the VP of Analytics of Paradigm Technology. He is an accomplished Senior Executive with decades of management consulting expertise. Mo has held various leadership positions including Senior Executive at Accenture, Partner at IBM, Partner at Capco, and Executive Director at Ernst & Young LLP.

Mr. Sahgal LinkedIn profile can be found here.

Paradigm Technology is a strategic consulting company serving the utilities, banking, airline, manufacturing, high-tech and retail marketplaces. We utilize innovative business and technology solutions to help clients enable their digital transformation programs, and improve their Analytics, Cloud, Master Data Management, and Project Leadership solution delivery. Paradigm is ready to support you in your business journey. For more information about Paradigm Technology, email or visit us at