Identifying strategies suggest a technique to achieve the goals given what one now knows about the possibilities and restraints. A well-known example of a programmatic strategy is the relationship or "bubble" diagram. These diagrams showed what functions should be near each other for the project to function smoothly.Relationship diagrams can also indicate the required circulation connections between spaces, what spaces need security or audio privacy, or other facets of special relations. Other sorts of strategies return in programs for many differing types of projects.

Some examples of similar categories of programmatic strategies include:

* Centralization and decentralization: What function parts are grouped together and which are segregated? For instance, in some offices the duplicating function is centralized, while in others there are copiers for each department.

* Adaptability: What types of changes are anticipated for diverse functions? Do facilities need to switch over a period of one or two hours?

* Flow: What products, services, and folks move through the project? What's required at every step to accommodate that flow?

* Concerns and phasing: What are the most significant functions of the project? What might be added later? Are there continuing existing operations that must definitely be maintained?

* Levels of access: Who is authorized where? What security levels are there? Ideally, every one of the goals and objectives identified in Step two will have some variety of plans for addressing that goal. Otherwise, either the goal isn't crucial, or even more discourse is needed to address the right way to achieve that goal or target.