“Create a top-down functional decomposition of managing customer support. Break it into handling incoming requests, resolving customer requests, and improving the support service. Show handling incoming requests breaking into capturing request details and categorizing and prioritizing; resolving customer requests breaking into diagnosing the issue and providing resolution and updating the customer; and improving the support service breaking into analyzing recurring issues and maintaining the knowledge base.”
Read the decisions behind it.
The top function is a broad business capability rather than a single task.
Three sub-functions separate request intake, resolution, and ongoing service improvement.
Two leaf functions beneath each sub-function keep the first-level breakdown readable at card size.
The arrows show decomposition relationships, not a time sequence or approval workflow.
Use this hierarchy to define scope, assign ownership, or decide which function needs deeper analysis. Use a process flowchart when the order of steps, decisions, and handoffs is the main question.
Other examples in this family.
Common questions
What is functional decomposition?
It is a hierarchical breakdown of one capability into major functions and smaller supporting functions.
How do I make a functional decomposition diagram?
Start with one top function, add three or four major sub-functions, then break each one into clear leaf functions.
How do I read a functional decomposition diagram?
Read from the top function downward. Each lower level explains the functions that make the function above possible.
Is functional decomposition the same as a process flowchart?
No. Functional decomposition shows scope and hierarchy, while a process flowchart shows the order of steps and decisions.
Do I need an account?
Yes, a free one. No card is asked for.