Think about making a simple maze game on a computer. 'Make a maze game' is too big to do in one go, so break it up: draw the maze, move the player with the arrow keys, stop the player at walls, and show 'You win' at the exit. Each of these is a job you can do and test by itself. Moving the player does not depend on how the 'You win' message looks.
Some parts are still too big, so you break them again. 'Draw the maze' becomes 'draw the outside walls', 'draw the inside walls', and 'mark the start and the exit'. You stop splitting when each piece is small enough to do. Then you plan how the pieces join: the walls made by the drawing part are the same walls the 'stop at walls' part checks.
Splitting a job is not always good decomposition. Suppose two friends write a story and one writes all the nouns while the other writes all the verbs. The work is split, but neither person can finish anything alone, because every sentence needs both. Cutting a job into 50 tiny jobs causes trouble too: putting them back together becomes harder than the job itself. Good parts can be finished on their own and fit together cleanly at the end.
Think of it like this. Decomposition is how a pizza shop handles a big order: one person makes the dough, one adds sauce and toppings, one runs the oven, and one boxes the pizzas. Each job can be done well by itself, and the jobs fit together at the end. If the jobs get too tiny, like one person per topping, passing the pizza around takes longer than making it.
Core idea. Solve each small independent part, then combine the solutions into a complete answer.