Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Map delivery work
List diagnosis, preparation, implementation, review and support per client type. Use observed times or explicit ranges and flag missing data. Include coordination and correction. Identify single-person tasks to locate the actual growth constraint rather than counting production hours alone.
Model availability and variation
Subtract current commitments, absences and management time before assigning new work. Model a demanding scenario as well as a typical one. Do not sell every available hour; incidents and waiting consume attention. Review with actual owners and record assumptions affecting start dates.
Test the acceptance limit
Example: several sites can be designed, but only one person reviews integrations. Schedule around review capacity, not just designers. Accept new commitments with named owners, review slots and support coverage. Otherwise offer a later start or smaller scope instead of hiding overload.
Key takeaways
- Available capacity depends on complete delivery and its bottlenecks.