Pattern: Invisible Requirements

• A narrow focus on functional and nonfunctional requirements for the design of business policies, procedures, processes and supporting IT solutions.
• The assumption that an IT application is the root cause of a problem.
• The Software is easier to change than structure, policy and culture.
• Political motivation to avoid dealing with root cause and find a scapegoat (e.g. IT department or IT Service Provider).

• The desired business outcomes are not delivered.

• Wasted time and resources – money.
• Increased frustration and lack of confidence in policies, documented processes, procedures and IT systems.
• High impact risks undocumented.

• Explore user/stakeholder ‘day-in-the-life’ stories using Values, Policies, Events, Content and Trusts dimensions to frame.
• Start with the Values of all individuals, roles, groups of users, decision makers and other influencing groups, entities, or bodies. These will reflect the motivations and outcomes expected of all participating in, or accountable for, the problem domain.
• Based on those Values, have Subject Matter Experts describe the Policies, Events and Content in the various ‘Day-in-the-life’ story.
• Finally, facilitate a cross-party discussion around the Trust dimension; explore the strength and impact of trust relationships and the levels of shared confidence in people, processes, information and technology.

Links to related posts:

This blog and its contents are freely available for use under

Creative Commons: Attribution + ShareAlike License.