Use the DoView Board prompt package already supplied in this chat.

Use this prompt to create a demo DoView Board for the organization or initiative named by the user.

If the user has not named the organization or initiative, ask for it before doing anything else.

This is not an endorsed or official board. It is only to show what a DoView Board for this organization could look like.

In the top right-hand text area, write:

Demo Only — Not Endorsed

Before building the board, ask the user only the questions needed to create a useful demo version.

Ask:

1. Should the demo be built from:

- public internet information

- documents the user uploads

- both public internet information and uploaded documents

- only information the user types into the chat

2. What type of organization or initiative is this?

- company

- government agency

- nonprofit

- voluntary club

- public-sector initiative

- internal program

- other

3. Should the demo board be:

- simple

- normal

- fuller strategy/evaluation example

4. Are there any areas, services, products, programs, projects, activities, outcomes or stakeholders that must be included?

5. Are there any areas that should be avoided or treated carefully?

After the user answers, build a populated demo DoView Board using the DoView Board prompt package.

The board should show how a DoView Board can connect outcomes, causal logic, projects or activities, teams or groups, competencies, measures, evaluation questions, and performance/evaluation documentation.

Use public information and/or uploaded material to look for the organization’s own language. Where available, use the organization’s actual names for:

- projects, programs, activities, initiatives or workstreams

- teams, groups, branches, divisions, functions or units

- competencies, capabilities, values, standards, skills or practice areas

Where actual names are not available, create plausible illustrative placeholders. Mark uncertain or created content clearly as illustrative.

Build the board with this structure:

1. Overview page

Include navigation to the main pages, including:

- Final Outcomes page

- outcome pathway pages

- Projects, Activities and Initiatives level 1 How page

- Teams, Groups and Functions level 2 How page

- no-level Competencies and Capabilities How page

- Performance and Evaluation Plan page

2. Final Outcomes page

Create 4-6 high-level final outcomes that make sense for the organization.

Use outcomes that describe real value for users, customers, stakeholders, communities, staff, funders, owners, partners or the public.

Keep outcome labels short and clear.

Do not put priorities or traffic lights on any boxes.

3. Outcome pathway pages

Create enough outcome pathway pages to give a reasonably rich picture of the organization’s This–Then logic.

As a guide, create about 3-5 outcome pathway pages for a simple demo and 5-7 pages for a fuller demo. Use fewer only if the organization or initiative is genuinely narrow.

Do not put “This–Then” after the page names. Page names should be short topic names, such as “Service Access,” “User Experience,” “Trust and Engagement,” or “Continuous Improvement.”

Each outcome pathway page must have a reasonable number of boxes. Do not create thin pages with only two or three boxes. As a guide, each outcome pathway page should usually contain about 6-10 boxes, unless the logic genuinely requires fewer.

Do not use a stereotyped page layout. Do not give every outcome pathway page the same number of columns, rows, boxes, links, measures or evaluation questions.

Vary the shape of the pathway pages according to the logic being shown. Some pages may have more steps, some may branch, some may converge, and some may have more than one end box.

Each outcome pathway page should:

- have short box labels

- show a clear left-to-right causal pathway

- include actual links between boxes in the DoView Board data structure

- include specific link Display Text explaining the actual rationale, assumption, evidence or organizational logic for that particular causal connection

- avoid putting Display Text under boxes

- include at least one end or near-end box with at least one attached measure

- include at least one end or near-end box with at least one attached evaluation question

Measures and evaluation questions must be associated with specific boxes on the outcome pathway pages. Do not create measures or evaluation questions that are only listed separately and not attached to any box.

Do not use generic placeholder link text.

Do not use repeated stock phrases such as:

- “Assumption: earlier conditions make this result more likely”

- “This supports the next step”

- “This contributes to the outcome”

- “Improved capability leads to better results”

- “Activities support outcomes”

Each item of link Display Text must be specific to the two boxes it connects. It should briefly explain why that specific earlier box is expected to influence that specific later box.

Do not make all link values on any page the same. Use varied link values where appropriate to show stronger, weaker, direct, indirect, or supporting relationships.

Do not put traffic lights on links between boxes on outcome pathway pages.

Do not put traffic lights on any boxes.

Do not put priorities on any boxes.

4. Level 1 How page

Create a level 1 How page called something like:

Projects, Activities and Initiatives (Illustrative)

Use the organization’s own terminology if it uses a better term, such as Programs, Workstreams, Services, Activities, Projects or Initiatives.

Do not use the word “Priorities” unless the organization itself uses that term.

Include plausible or publicly identified projects, activities, programs, initiatives or workstreams.

This page must have vertical links to boxes on the outcome pathway pages.

The board is incomplete if the level 1 How page does not have vertical links to outcome pathway boxes.

Create at least 8 credible vertical links from level 1 How page boxes to boxes on the outcome pathway pages.

Each level 1 How page box should usually link to more than one relevant outcome pathway box.

Each outcome pathway page should receive at least one vertical link from the level 1 How page.

Do not merely mention the mapping in text. Create actual vertical links in the DoView Board data structure.

Each vertical link must connect a specific level 1 How page box to a specific outcome pathway box.

Each vertical link should make sense in relation to the project, activity, program, initiative or workstream and the outcome pathway box it supports.

Use enough links to show that the level 1 How page is genuinely mapped onto the outcome pathway pages, not merely attached to them.

Do not make all vertical link values the same.

Do not put priorities on any boxes.

Do not put traffic lights on any boxes.

Do not put traffic lights on these vertical links.

5. Level 2 How page

Create a level 2 How page called something like:

Teams, Groups and Functions (Illustrative)

Use the organization’s own terminology if it uses a better term, such as Teams, Groups, Branches, Divisions, Units, Functions or Departments.

Include plausible or publicly identified teams, groups, functions or units.

This page must have vertical links to boxes on the level 1 How page.

The board is incomplete if the level 2 How page does not have vertical links to level 1 How page boxes.

Create at least 8 credible vertical links from level 2 How page boxes to boxes on the level 1 How page.

Each level 2 How page box should usually link to more than one relevant level 1 project, activity, program, initiative or workstream box.

Do not merely mention the mapping in text. Create actual vertical links in the DoView Board data structure.

Each vertical link must connect a specific level 2 How page box to a specific level 1 How page box.

Each vertical link should make sense in relation to the team, group, function or unit and the level 1 project, activity, program, initiative or workstream it supports.

Use enough links to show that the level 2 How page is genuinely mapped onto the level 1 How page, not merely attached to it.

Do not make all vertical link values the same.

Do not put priorities on any boxes.

Do not put traffic lights on any boxes.

Do not put traffic lights on these vertical links.

6. No-level cross-link How page

Create a no-level How page called something like:

Competencies and Capabilities (Illustrative)

Use the organization’s own terminology if it uses a better term, such as Competencies, Capabilities, Skills, Practice Areas, Standards, Values or Ways of Working.

Include competencies or capabilities that are relevant to the organization and its work.

This must be a no-level How page, not level 1 and not level 2.

This page must have cross-links to boxes on:

- the outcome pathway pages

- the level 1 How page

- the level 2 How page

The board is incomplete if the competencies page does not have cross-links to all three of these areas.

Create at least:

- 8 cross-links from competencies to outcome pathway boxes

- 8 cross-links from competencies to level 1 How page boxes

- 8 cross-links from competencies to level 2 How page boxes

Do not create a stereotyped pattern where each competency has the same number of links.

Do not create only one or two cross-links per competency by default.

Some competencies should have several links. Some should have fewer. The pattern should reflect the logic of the organization, not a mechanical template.

At least three competencies must each have three or more cross-links.

At least one competency must link to boxes on all three areas: outcome pathway pages, level 1 How page, and level 2 How page.

Do not merely mention the mapping in text. Create actual cross-links in the DoView Board data structure.

Each cross-link must connect a specific competency or capability box to a specific box on another page.

Each cross-link should make sense in relation to the competency or capability and the box it supports.

Use enough cross-links to show that competencies can genuinely support outcomes, projects/activities and teams/groups.

Do not make all cross-link values the same.

Do not put priorities on any boxes.

Do not put traffic lights on any boxes.

Do not put traffic lights on these cross-links.

7. Measures

Create a small but useful set of practical measures for the board.

Every measure must be attached to a specific relevant box on an outcome pathway page.

Do not create free-floating measures that are not associated with boxes.

Attach measures mainly to end or near-end boxes, but also use earlier boxes where a leading measure would be useful.

Use a mix of leading, intermediate and outcome measures where useful.

Keep measures concise.

Measures should help show whether progress is being made, whether services or activities are working, whether stakeholders are experiencing intended benefits, and whether the organization is improving over time.

Do not put priorities or traffic lights on measure boxes.

8. Evaluation questions

Create a small but useful set of evaluation questions.

Every evaluation question must be attached to a specific relevant box on an outcome pathway page.

Do not create free-floating evaluation questions that are not associated with boxes.

Attach evaluation questions mainly to end or near-end boxes, but also use earlier boxes where a process, implementation or causal-assumption question would be useful.

The questions should help users assess:

- whether the causal logic is working

- whether projects or activities are contributing to outcomes

- whether users, customers, stakeholders or communities are experiencing intended benefits

- whether there are important differences between groups or locations

- whether risks, barriers or unintended consequences are emerging

- whether anything should be stopped, changed, scaled or better measured

Keep evaluation questions concise and practical.

Do not put priorities or traffic lights on evaluation question boxes.

9. Performance and Evaluation Plan page

Create a documentation page called:

Performance and Evaluation Plan

Use this page to show how the DoView Board can support performance monitoring, evaluation planning, learning and improvement.

This page should contain a little explanatory content, not just cloned boxes. Keep it concise, but make it clear that it is a performance and evaluation plan.

Include short sections with these headings:

- Purpose

- Outcomes to be tracked

- Measures

- Evaluation questions

- How the board will be used

- Review and learning cycle

- What needs validation

- Limitations and disclaimer

Under Purpose, briefly explain that the plan shows how the organization could monitor progress, test the outcome logic, and use evidence to improve projects, activities and services.

Under Outcomes to be tracked, use clones of the relevant final outcomes and any important outcome pathway boxes mentioned.

Under Measures, use clones of all measures mentioned. Add a short note explaining whether the measures are leading, intermediate or outcome measures where useful.

Under Evaluation questions, use clones of all evaluation questions mentioned. Add a short note explaining what each question is intended to test or clarify.

Under How the board will be used, briefly explain how outcome pathways, projects or activities, teams or groups, and competencies are connected through vertical links and cross-links.

Under Review and learning cycle, briefly describe a simple review rhythm, such as quarterly performance review and annual evaluation review. Keep this generic and illustrative.

Under What needs validation, briefly list the main parts that would need to be checked with people inside the organization.

Under Limitations and disclaimer, state that the board is Demo Only, Not Endorsed, and based on public information, uploaded information or illustrative organizational logic.

Use clones on this page whenever referring to board elements.

The Performance and Evaluation Plan page must contain clones of every box, final outcome, measure and evaluation question that it mentions.

Do not retype any box label, outcome, measure or evaluation question as ordinary text when it can be shown as a clone.

Use clones on this page to list:

- all boxes mentioned in the plan

- all final outcomes mentioned in the plan

- all measures mentioned in the plan

- all evaluation questions mentioned in the plan

- selected projects, activities or initiatives where useful

- selected teams, groups or functions where useful

- selected competencies or capabilities where useful

If the page summarizes a box, measure or evaluation question, include the relevant clone beside or directly below the summary so users can see how documentation stays connected to the board.

Do not make this page too long. It should be clear enough to demonstrate a performance and evaluation plan in a short help video.

10. Link and layout rules

Create actual links in the DoView Board data structure. Do not only describe links in text.

Outcome pathway pages must include links between boxes.

Level 1 How page boxes must have actual vertical links to outcome pathway boxes.

Level 2 How page boxes must have actual vertical links to level 1 How page boxes.

The no-level competencies page must have actual cross-links to outcome pathway boxes, level 1 How page boxes and level 2 How page boxes.

Do not create tokenistic single-link mapping.

The level 1 How page must have at least 8 actual vertical links to outcome pathway boxes.

Every outcome pathway page must receive at least one actual vertical link from the level 1 How page.

The level 2 How page must have at least 8 actual vertical links to level 1 How page boxes.

The no-level competencies page must have at least 8 actual cross-links to outcome pathway boxes.

The no-level competencies page must have at least 8 actual cross-links to level 1 How page boxes.

The no-level competencies page must have at least 8 actual cross-links to level 2 How page boxes.

Do not use a mechanical cross-link pattern. Do not give every competency the same number of links.

At least three competencies must each have three or more cross-links.

At least one competency must link to boxes in all three areas: outcome pathway pages, level 1 How page, and level 2 How page.

Do not create a board that looks mechanically generated. Page layouts, pathway depth, branching, measures, evaluation questions and links should vary according to the actual logic of the organization or initiative.

Do not put traffic lights on links between boxes on outcome pathway pages.

Do not put traffic lights on any boxes.

Do not put priorities on any boxes.

Do not use gray traffic lights anywhere.

For this demo board, avoid traffic lights entirely unless the DoView Board prompt package requires them for a specific structure.

Do not make a page where all link values are 1.

Use varied link values where appropriate.

For links between boxes on outcome pathway pages, include Display Text where it helps explain the rationale, evidence or organization-specific assumption for the causal connection.

Do not use generic placeholder link Display Text.

Do not use repeated stock phrases such as:

- “Assumption: earlier conditions make this result more likely”

- “This supports the next step”

- “This contributes to the outcome”

- “Improved capability leads to better results”

- “Activities support outcomes”

Each item of link Display Text must be specific to the two boxes it connects. It must briefly explain why that specific earlier box is expected to influence that specific later box.

Do not use Display Text under boxes.

11. Board style

Keep the board simple enough to understand quickly, but not so sparse that it looks unfinished.

Use short box labels.

Use plain language.

Use This–Then logic on the outcome pathway pages, but do not put “This–Then” in the page titles.

Do not turn the board into a task list, organization chart or strategy document.

Do not put Display Text under boxes.

Only use Display Text where it helps explain links between boxes, especially the rationale, evidence or organization-specific assumption behind links on outcome pathway pages.

Make assumptions visible through specific link Display Text, the Performance and Evaluation Plan page, or documentation notes. Do not use generic assumption placeholders.

Do not imply that the organization has approved, endorsed or verified the board.

If using public internet information, include a short source note on the Performance and Evaluation Plan page.

12. Final validation before output

Before finishing, check that:

- the top right-hand text says “Demo Only — Not Endorsed”

- there are enough outcome pathway pages to give a reasonably rich picture of the organization’s This–Then logic

- there are 3-5 outcome pathway pages for a simple demo or 5-7 pages for a fuller demo, unless the organization or initiative is genuinely narrow

- outcome pathway page names do not include “This–Then”

- each outcome pathway page has a reasonable number of boxes

- outcome pathway pages do not all use the same stereotyped number of columns, rows, boxes, links, measures or evaluation questions

- each outcome pathway page has a layout shaped by the logic of that page, not a repeated template

- no box has a priority

- no box has a traffic light

- no outcome pathway box link has a traffic light

- every measure is attached to a specific relevant box on an outcome pathway page

- every evaluation question is attached to a specific relevant box on an outcome pathway page

- there are no free-floating measures or evaluation questions that are only listed separately

- the level 1 How page has at least 8 actual vertical links to outcome pathway boxes

- every outcome pathway page receives at least one vertical link from the level 1 How page

- the level 2 How page has at least 8 actual vertical links to level 1 How page boxes

- the no-level competencies page has at least 8 actual cross-links to outcome pathway boxes

- the no-level competencies page has at least 8 actual cross-links to level 1 How page boxes

- the no-level competencies page has at least 8 actual cross-links to level 2 How page boxes

- at least three competencies each have three or more cross-links

- at least one competency links to all three areas: outcome pathway pages, level 1 How page and level 2 How page

- the cross-link pattern is not mechanical or stereotyped

- link Display Text between outcome pathway boxes is specific and not generic placeholder text

- no repeated placeholder phrase such as “Assumption: earlier conditions make this result more likely” has been used

- the Performance and Evaluation Plan page has enough explanatory text to read as a concise performance and evaluation plan, not just a list of clones

- the Performance and Evaluation Plan page uses clones for every box, final outcome, measure and evaluation question it mentions

- no Display Text has been placed under boxes

- the complete standalone HTML DoView Board opens with the normal DoView Board controls

If any of these checks fail, fix the board before producing the final output.

After building and validating the board, produce the complete standalone HTML DoView Board.