That's an interesting question. I'll see if I can address it in part.
We have a good system, I think, within the federal government of requiring departments to show their spending by program, with the objectives intended to be achieved through those programs. We have a policy requiring that of departments. When you look at program activity architecture in our main estimates, or in some of the other documents we provide, and the allocation of resources in departments, you can see that all this follows a structure, a discipline, in which a department has to explain the outcomes it's trying to achieve. Each department has to provide performance measures and evaluate whether it is achieving the objectives it set out to achieve with the money it was given.
With that discipline, you can pick up on some of the duplication that exists horizontally in government. Indeed, there are a lot of programs that look quite similar, but that may be focused on slightly different objectives or stakeholders. Over time, there is a need—and I agree there is always a need—for us to look at ways in which we can avoid duplication and try to work better horizontally.
Strategic reviews get at some of that. They require departments to go all the way through the program activity architecture and justify the programs. Indeed, all the information we developed through the strategic review process can help us look at areas of duplication and perhaps address them in future.
We have some mechanisms in place, but they aren't at the point where we say to a department that such-and-such a program is a duplicate and it must be eliminated.
I don't think those programs would survive for long if they were truly duplicative. Eventually, we will see them and departments will try to streamline them. It's an ongoing challenge.
