Four worked structures

Four scenarios. Facts, structure, reasoning. One. A single-business-unit consultancy, two hundred people. One business unit, one project unit, a handful of classified organizations. The base case — and simple is correct when the facts are simple. Two. Two business units with a shared delivery pool. One project unit associated with both. Expenditure classification across all delivery organizations. And a preview of the cross-charge question. Three. An internal IT department in a large enterprise. One business unit, one project unit, no billing — and expenditure classification across every department that consumes IT project effort. Four. An engineering firm with capital and contract projects. One project unit — with project types doing the differentiation rather than the org structure. MANY DIFFERENCES CLIENTS WANT TO EXPRESS IN THE ORG STRUCTURE BELONG IN PROJECT TYPES INSTEAD. This scenario exists to make that point — Module 7 is where those differences live, and reaching for…

In this module: Module 3 · Organization Structures

1. 1What we are building
2. 2The decision you cannot undo
3. 3The organization object model
4. 4The project unit
5. 5Owning versus expenditure organizations
6. 6Running the structure design workshop
7. 7Four worked structures
8. 8Business units and the project accounting function
9. 9Creating organizations
10. 10Classifying organizations
11. 11Organization hierarchies
12. 12Creating project units
13. 13Project unit options
14. 14Reference data set assignments
15. 15Associating project units with business units
16. 16Proving the structure works
17. 17What breaks
18. 18Lab briefing: Meridian Consulting
19. 19Lab solution walkthrough