1.1 Welcome: Why New Departments Succeed or Fail (Start Here)
A new department is a function that did not exist before: a team, a budget and a mandate created because the organisation needed something it was not getting. Starting one is different from running one. There is no plan, no team and no track record, and every early choice sets a pattern.
Who this course is for
The course is for people appointed to head a function that does not yet exist, for leaders who commission one, for consultants who design one, and for staff preparing for that step. It applies to any function: internal audit, risk, revenue assurance, performance management, software development, training, compliance, data or customer experience. The story follows Mwila Chanda, newly appointed Head of Revenue Assurance at the fictional Kuvanya Group, through her first 100 days.
How new departments come about, and why they are judged early
A chief executive asks for one; a board, audit committee or consultant recommends one; a regulator expects one; growth or a crisis shows that no one owns a risk. However it starts, the department is watched from the first week. Some colleagues welcome it, some doubt it is needed, and a few may hope it fails because it questions their work or adds to their load.
The Five Keys
This course is built on the Five Keys. Each key answers one question and has its own principles, methodology and toolkit.
| Key | The question it answers | Principles beneath it | Methodology | Toolkit |
|---|---|---|---|---|
| Problem Definition | Why does this department exist, and what problem does it solve? | Purpose before structure; Value beyond compliance; One clear identity | Mandate Discovery | Lesson 1.4 |
| Documentation Tools | What must be written down first? | Start with something, then improve; Alignment by cascade | Minimum Viable Documentation | Lesson 2.4 |
| Culture | How must people here behave, given the work? | Culture by design, fitted to the work; The leader models the culture | Culture by Design | Lesson 3.4 |
| Personal Recruitment | Who joins, on what basis, and how do we know they fit? | Accountability stops with the head; Recruitment is a business decision | Culture-Fit Recruitment and Confirmation | Lesson 4.4 |
| Quick Wins | What early value can we release, and when? | Earn legitimacy early, release value wisely | Quick Win Release | Lesson 5.4 |
Problem Definition is the foundation: the plan, the culture, the people and the wins all depend on it.
The Five Keys is a framework developed by Eunoia Consultants from practical experience of starting new departments. This course explains it in its own words. It does not use or endorse any proprietary assessment, model or training programme, and it is not endorsed by any institute or organisation.
About the case company: Kuvanya Group, its subsidiaries (Kuvanya Bank, KuvaTel, KuvaPay, Kuvanya Mining Supplies and Kuvanya Shared Services), its new Group Revenue Assurance department, its client “the Power Authority” and every person named in this course are fictional. They were created by EunoiaData for teaching purposes only. Any resemblance to real organisations or people is coincidental. Countries, laws and regulators are real and are described as they stood in 2026.
How this course works
There are five modules, one for each key. Lessons 1 to 3 explain the key and end with three views (the department head’s, the sponsor’s and a colleague’s in another department); lesson 4 is a toolkit you can adapt. Most lessons include a worked example with a Try it note.
| Toolkit | Lesson | What it helps you do |
|---|---|---|
| Mandate Discovery guide, Problem Definition canvas, sponsor sign-off | 1.4 | Agree why the department exists |
| Strategy plan, cascade table, starter templates, document register | 2.4 | Write only what you need, first |
| Culture charter, rituals plan, leader commitments | 3.4 | Design the way the team works |
| Role profile, interview guide, probation record, decision record | 4.4 | Recruit and confirm the founding team |
| Stakeholder map, quick-win register, release schedule, 100-day plan | 5.4 | Release value and plan the first 100 days |
Outside this course: leading a team day to day is in First-Time Manager Toolkit (course 50); influence and office politics in depth are in Navigating Office Politics (course 11); the law on hiring and probation in each country is in the labour-law courses listed in lesson 5.4.
Worked example W1: Mwila’s Five Keys self-check, day 1 and day 100
| Key | Day 1 score | Day 1 evidence | Day 100 score | Day 100 evidence |
|---|---|---|---|---|
| Problem Definition | 2 | A two-line request from the CEO and a consultant’s report | 5 | Problem, value and identity statements signed off by the sponsor |
| Documentation Tools | 1 | No plan, no templates, a borrowed spreadsheet | 4 | Strategy plan and cascade table approved; nine of ten documents in use |
| Culture | 1 | Not yet thought about | 4 | Four values with behaviours; five rituals and commitments running |
| Personal Recruitment | 2 | HR offered two internal transfers | 4 | Four founding hires chosen on culture and skill; probation objectives set on day one |
| Quick Wins | 1 | Pressure to ‘find something’ in the first month | 4 | Six wins released, the held one last; two in the pipeline |
| Total (out of 25) | 7 | Weakest: documentation, culture, quick wins | 21 | Every key at 4 or above |
What it shows: Mwila scored herself honestly on day 1 and again on day 100; her total rose from 7 to 21 out of 25. The low day-1 scores were not failures: she had just arrived. They told her where to start.
Try it: Score your own department, or one you know, from 1 (nothing in place) to 5 (in place and working) on each key, with one line of evidence each. If Problem Definition is below 4, start there.
Example: on her first morning in Harare, Mwila Chanda, newly appointed Head of Revenue Assurance, receives a two-line note from Joseph Mwale, Group CEO (“set up revenue assurance and stop the leakage”) and a consultant’s report. She has no team, no plan and a borrowed desk. Before booking a meeting she scores herself against the five keys: 7 out of 25. She starts with the problem, because everything else depends on it.
Three views
- As the department head: You will be tempted to show activity in week one. Understand the problem first; activity in the wrong direction is hard to undo.
- As the sponsor: Say plainly why you created the department, make time for the new head, and expect questions before results.
- As a colleague in another department: Ask the new head what the department is for and how it will work with your team; you are entitled to a clear answer.
Check before you act: Examples use the fictional Kuvanya Group, its people and figures for illustration only. Adapt each tool to your organisation, its policies and the department you are building.
Key takeaway
A new department is judged early, and most fail for reasons that have nothing to do with technical skill. The Five Keys give you an order: define the problem first, then document, shape the culture, recruit and release early wins.
Enjoyed this lesson? Get the full course: Starting a New Department Toolkit: Five Keys to Building a Function That Lasts
Unlock every lesson, the module quizzes and your certificate on completion.