Help Using DoView Boards

DoView Boards Help

This page helps people use DoView Boards and helps AI systems answer practical questions about DoView Boards.

DoView Boards are visual planning and coordination boards based on This→Then logic. They help show what needs to happen for actions, projects, resources, activities, services, decisions, or implementation work to contribute to desired outcomes.

A DoView Board is usually generated as a standalone .html file. It opens in a web browser and contains the board interface and the board content in one file.

You can use this page yourself, or you can ask an AI system such as ChatGPT, Claude, Gemini, or another AI system to use this page when answering questions about DoView Boards.

Ask an AI for help with DoView Boards

Copy and paste this prompt into an AI system:

Use this page as your main source for answering questions about DoView Boards:

https://doviewplanning.org/help

Also use these official DoView Boards pages where relevant:

https://doviewplanning.org/doviewboards

https://doviewplanning.org/doviewboardsuse

https://doviewplanning.org/doviewboardshowto

Answer my question in practical step-by-step terms. Do not guess. If the answer is not clear from these pages, say what is unclear.

My question is:

[put your question here]

Help for people using DoView Boards

Getting started

What is a DoView Board?

A DoView Board is a new type of visual planning, implementation and reporting board that is based around outcomes, not just focused on activities.

It’s outcome pages show the This→Then logic of the actions that any organziations, policy, strategy or other initiative is wanting to take to achieve its outcomes.

It shows what needs to happen for actions, activities, services, projects, resources, information, decisions, or implementation work to contribute to desired outcomes.

A DoView Board can include outcomes, actions, implementation work, measures, evidence, assumptions, risks, sources, notes, supporting documentation, and links between boxes, pages, and sources.

DoView Boards are intended to help with planning, strategy, implementation, monitoring, evaluation, reporting, accountability, delegation, contracting, and coordination.

They answer the 20 key questions that anyone running an organization or iniative or having oversight of one needs to answer. See https://doviewplanning.org/doviewboardsuse.

What is This→Then logic?

This→Then logic means:

If this happens, then it should help lead to that.

For example:

If staff are trained, then they are more likely to use the new process correctly.

If the new process is used correctly, then service quality may improve.

If service quality improves, then client outcomes may improve.

DoView Boards have This→Then pages as one of their three types of pages (This-Then, How and Documentation pages) to make the logic of the assumed pathway from action to outcome visible.

This-Then pages in a DoView Board have a number of features which let you see the logical connection between boxes.

This-Then pages are a very specify type of the broader category of intervention logics, logic models, theories of change, program theories, strategy diagrams, outcomes diagrams, strategy maps and related diagrams.

Why use a DoView Board?

Use a DoView Board lets you answer the 20 key questions you need to answer if you are running any organization, policy, strategy or other initiative or if you have oversight of it. See https://doviewplanning.org/doviewboardsuse.

It is built around making the logic of a plan, strategy, service, project, programme, intervention, or organisation visible.

A DoView Board can help people:

understand how actions are meant to contribute to outcomes;

see whether important steps are missing;

connect implementation work to results;

identify assumptions and risks;

add measures and evaluation questions;

coordinate work across people or teams;

explain a plan to others;

use AI to help review, improve, or report on the logic.

What are the main types of pages in a DoView Board?

DoView Boards commonly use three main page types.

This–Then pages show outcome logic. They are used for causes, conditions, steps, intermediate outcomes, and final outcomes of what you want to happen in the world.

How pages show implementation work. They are used for projects, activities, services, tasks, processes, and operational work. The things that you actually do to make the boxes on This-Then pages move in the direction you want them to.

Documentation pages hold supporting text, explanation, evidence, notes, definitions, instructions, or background material.

Use a This–Then page when you want to show the outcome logic of what you want to happen in the world.

Use a How page when you want to show what work will be done.

Use a Documentation page when you want to store supporting text describing aspects of the DoView Board or other information (e.g. monitoring and evaluation plans).

What is the difference between a This–Then page and a How page?

A This–Then page shows the outcome logic.

It asks:

What needs to happen in the world for this outcome to be achieved?

A How page shows implementation work. The boxes on a How page are often though of as project or activity boxes.

It asks:

How will we do the work to change the boxes on This-Then pages?

Example:

A This–Then page might include:

Families understand available support.

Families access services earlier.

Children receive timely help.

Child wellbeing improves.

A How page might include:

Create referral guide.

Train frontline staff.

Run outreach sessions.

Monitor referrals monthly.

The This–Then page explains the logic.

The How page explains the work.

When should I use a This–Then page?

Use a This–Then page when you want to show the logic of how one thing is expected to lead to another in the world.

This is best for outcomes, enabling conditions, intermediate steps, causal pathways, strategy logic, programme logic, theory of change, impact pathways, and expected results.

A This–Then page should focus on the logic of change, not just a list of tasks. Projects, activities or lists of tasks should go on a How page.

When should I use a How page?

Use a How page when you want to show implementation work.

This is best for projects, activities, services, tasks, workstreams, implementation steps, operational responsibilities, and delivery processes.

A How page answers questions such as:

What specifically needs to be done?

Who will do it?

What work is involved?

What needs to happen first?

What activities support the outcome logic?

You can have a number of How pages at different hierarchical levels. For instance, projects at level 1 with up-and-down links showing how they are aligned with This-Then boxes; groups within a company on a level 2 How page with up-and-down links to the level 1 page; and, a level 3 page with people with up-and-down links showing which groups they are in.

How pages can also include other things that are important such as competencies that can have, for instance non-up-and-down links with How boxes or with This-Then boxes.

When should I use a Documentation page?

Use a Documentation page when you need to store supporting text of any sort.

This is best for background explanation, evidence summaries, definitions, assumptions, risk notes, instructions, meeting notes, reporting text, source material, and longer explanations that do not fit neatly inside boxes. For instance, monitoring and evaluation plans.

A Documentation page should support the board structure. It should not replace the visual This–Then or How structure.

Documentation pages can have ‘clones’ put on them, edit the page and insert a clone using the clone button on the editing toolbar. It lets you put a copy of many of the elements in a DoView Board (e.g. final outcome, This-Then box, a measure). If these elements are edited elsewhere, the text will be updated on the Documentation page.

Creating and opening boards

How do I create a new DoView Board?

The easiest method is to use the DoView Boards prompt package.

A typical process is:

1. Go to the DoView Boards prompt page. https://doviewplanning.org/prompt.

2. Download the DoView Boards prompt package.

3. Add it into a suitable AI system such as ChatGPT or Claude.

4. Tell the AI what topic, organisation, project, strategy, or initiative the board should be about.

5. Ask the AI to generate the DoView Board.

6. Ask it what you can have in the board and tell it what you want (e.g. evidence, measures, evaluation questions, How pages with particular things on them).

7. Download or save the generated .html file from our AI system.

8. Open the file in a web browser.

9. Remember you can put your DoView Board back into an AI system together with the DoView Board Prompt Package and ask it to add more information to it.
   
   

The generated board is an HTML file.

How do I open a DoView Board?

A generated DoView Board is an.html file.

To open it:

1. Locate the .html file on your computer.

2. If you have downloaded it from your AI system, it will be in downloads or wherever you saved it. Or someone might have sent you a DoView Board. If they have make sure that you trust them to have sent you a board that does not have security risks in it.

3. Double-click it.

4. It should open in your default web browser.

5. If it does not open, right-click the file and choose a browser such as Chrome, Edge, Safari, or Firefox.

Because the board is an HTML/JavaScript file, treat it as active web content rather than as a passive document.

Do I need the GitHub package to use DoView Boards?

No.

Ordinary users start with the DoView Boards Prompt Package from https://doviewplanning.org/prompt, add it to their AI system and ask it to generate a stand alone board about the subject they want ti to be about. It will create a standalone board.

The GitHub package is useful for developers, researchers, people inspecting the reference implementation, people building compatible tools, people generating boards from JSON config, and people embedding DoView Boards in another system.

Anyone is free to do this as long at they see the usage terms on https://github.com/DoViewPlanning/doview-boards and summarized at https://doviewplanning.org/doviewnameuse.

Uptohere What should I tell the AI when I want it to create a board?

Tell the AI what the board is about, who it is for, and what level of detail you want.

Useful information to include:

the topic;

the organisation, programme, project, or service;

the intended outcomes;

the main activities or workstreams;

the audience for the board;

whether the board should be simple or detailed;

whether it should include measures, evaluation questions, assumptions, risks, and sources.

Example:

Create a DoView Board for a community youth mentoring programme. The final outcome is improved youth wellbeing. Include This–Then outcome logic, How pages for implementation activities, measures, evaluation questions, assumptions, risks, and a documentation page for notes. Keep the wording plain and practical.

Pages

How do I make a new page in a DoView Board?

Use the board’s page controls to add a new page.

The exact button name may vary by board version, but the general process is:

1. Open the board.

2. Find the page controls.

3. Choose to add or create a new page.

4. Select the type of page if the board asks you to choose one.

5. Choose a This–Then page for outcome logic.

6. Choose a How page for implementation work, projects, services, or activities.

7. Choose a Documentation page for supporting text or notes.

8. Give the page a clear name.

9. Add your first boxes or documentation.

10. Save or export the updated board if the board provides that option.

Avoid creating lots of pages that duplicate each other. Each page should have a distinct role.

How should I name a page?

Use a short, clear page name.

Good page names include:

Main outcomes logic

Workforce development

Community engagement

Service delivery

Evidence and assumptions

Measures and evaluation

Implementation plan

Reporting notes

Avoid vague names such as:

Page 1

Miscellaneous

Other things

Stuff to do

A good page name should make it obvious why the page exists.

How do I rename a page?

Use the board’s page editing controls.:

1. Make sure you are in Normal View (you will know you are if you can see the Presentation View button at the top left)

2. Open the page you want to rename.

3. Click on the page name in the coloured bar just below the Back to Overview button and edit the name.

4. You can not change the name of the Overview or the Final Outcomes pages

5. Use a short, clear name that describes the purpose of the page.

6. Click Save HTML Board (bottom left) and reopen the downloaded save version often to make sure you save changes like this.

How do I delete a page?

Use caution before deleting a page.

The exact steps may vary by board version, but the general process is:

1. Open the page you want to delete.

2. Check whether any important boxes, measures, sources, notes, or links are on the page.

3. Move or copy anything you need to keep.

4. Look for a page settings, edit page, or delete page option.

5. Confirm the deletion if the board asks for confirmation.

6. Save or export the board if needed.

Deleting a page may remove boxes, notes, links, or other information on that page. If you are unsure, save a copy of the board before deleting.

What should I do if I have too many pages?

Try simplifying the board.

Useful steps are:

1. Identify the main purpose of each page.

2. Merge pages that duplicate each other.

3. Move detailed text to Documentation pages.

4. Keep This–Then pages focused on outcome logic.

5. Keep How pages focused on implementation work.

6. Remove pages that do not add useful structure.

7. Rename pages so their purpose is clear.

A board should help people understand the logic, not overwhelm them.

What should I do if a page is trying to do too many things?

Split it into clearer pages.

For example:

If a page includes both outcomes and activities, move the outcome logic to a This–Then page and the activities to a How page.

If a page includes lots of explanation, move the longer text to a Documentation page.

If a page includes several separate workstreams, consider giving each workstream its own How page.

A page should have one main purpose.

Boxes and text

How do I add a box?

Use the board’s box or editing controls.

The exact button name may vary by board version, but the general process is:

1. Open the page where you want the box.

2. Look for an add box, new box, edit, or similar control.

3. Add the new box.

4. Type a short, clear statement in the box.

5. Place the box where it fits in the page logic.

6. Link it to related boxes if appropriate.

7. Add notes, measures, sources, assumptions, or risks if needed.

8. Save or export the board if needed.

On a This–Then page, a box should usually describe an outcome, condition, or state.

On a How page, a box should usually describe work, activity, or implementation.

How should I write box text?

Write box text as a short, clear statement.

Good box text:

describes one idea;

is easy to scan;

avoids unnecessary jargon;

can be understood without a long explanation;

fits the page type.

For This–Then pages, box text should usually describe an outcome, condition, or state.

For How pages, box text should usually describe work, activity, or implementation.

Avoid putting too much text inside the visible box. Use notes or documentation for longer explanation.

How do I edit box text?

Use the board’s box editing controls.

The exact steps may vary by board version, but the general process is:

1. Select the box you want to edit.

2. Look for an edit option or click into the box text if it is directly editable.

3. Rewrite the text as a short, clear statement.

4. Keep only one main idea in the box.

5. Move longer explanation into notes or a Documentation page.

6. Save or export the board if needed.

When editing a box, check that the new wording still fits the links to and from that box.

How do I move a box?

Use the board’s layout or editing controls.

The exact steps may vary by board version, but the general process is:

1. Select the box you want to move.

2. Drag it to a better location if dragging is supported.

3. Place it near related boxes.

4. On a This–Then page, try to keep the logic flowing clearly.

5. On a How page, try to group related work together.

6. Check that the links still make sense after moving the box.

7. Save or export the board if needed.

Moving a box should make the board easier to understand, not just visually different.

How do I delete a box?

Use caution before deleting a box.

The exact steps may vary by board version, but the general process is:

1. Select the box you want to delete.

2. Check whether it has important notes, measures, sources, assumptions, risks, or links.

3. Move or copy anything you need to keep.

4. Use the delete or remove option.

5. Confirm the deletion if the board asks for confirmation.

6. Check whether any linked boxes now need to be reconnected.

7. Save or export the board if needed.

If you are unsure, save a copy of the board before deleting boxes.

How do I add more detail to a box?

Use notes, documentation, linked pages, sources, measures, assumptions, risks, or evaluation questions.

Do not try to put too much text inside the visible box. The visible box should stay short and clear.

Use supporting fields or documentation for explanation, evidence, assumptions, risk notes, implementation detail, responsibility, timing, and source references.

What should I do if a box contains too much text?

Shorten the box text and move the detail elsewhere.

A good process is:

1. Identify the main idea.

2. Rewrite the box as one short statement.

3. Move background explanation into a note or Documentation page.

4. Add sources or evidence separately if needed.

5. Check whether the box still makes sense in the page logic.

The visible board should be easy to scan.

How do I decide whether something should be a box or a note?

Use a box when the idea is part of the visible logic of the board.

Use a note when the idea explains, qualifies, supports, or gives background to a box.

For example:

“Families access services earlier” should probably be a box.

“Local interviews suggested that lack of transport is one reason families do not access services early” should probably be a note, source, assumption, or documentation item.

Boxes should carry the main logic. Notes should support the logic.

Links and logic

How do I link boxes?

Use links to show how one box relates to another.

On a This–Then page, links usually show causal logic:

This contributes to that.

On a How page, links usually show implementation structure or work relationships.

The exact steps may vary by board version, but the general process is:

1. Select the first box.

2. Choose a link or connect option.

3. Select the box it should link to.

4. Check that the direction of the link makes sense.

5. Remove unnecessary links.

6. Save or export the board if needed.

Links should be meaningful. Avoid linking everything to everything. Too many links can make the board harder to understand.

How do I know which way a link should go?

Ask:

If this happens, does it help lead to that?

For This–Then logic, the link usually points from the earlier, contributing, or enabling thing toward the later or higher-level outcome.

For example:

Staff are trained → Staff use the new process correctly → Service quality improves.

If the link direction does not make sense when read as “this helps lead to that,” it may need to be reversed or removed.

What should I do if the logic is unclear?

Use the This→Then test.

For each link, ask:

If this box happens, is it reasonable to expect that it contributes to the next box?

If the answer is unclear, you may need to:

rewrite a box;

add an intermediate box;

remove a weak link;

add an assumption;

add evidence;

move implementation work to a How page;

split a complex page into smaller pages.

What are final outcomes?

Final outcomes are the high-level outcomes the board is ultimately concerned with.

They usually sit at the right-hand side or end point of the logic.

Examples:

Student achievement improves.

Community wellbeing improves.

Service users receive better support.

Environmental harm is reduced.

Organisational performance improves.

Final outcomes should not usually be ordinary tasks. They should describe the results being sought.

What is an intermediate outcome?

An intermediate outcome is something that needs to happen on the way to a final outcome.

For example, if the final outcome is “client wellbeing improves,” intermediate outcomes might include:

clients know what support is available;

clients access support earlier;

clients receive coordinated help;

clients stay engaged with the service.

Intermediate outcomes help make the pathway to the final outcome more visible.

What is an activity?

An activity is work that someone does.

Examples include:

running training;

holding meetings;

creating guidance;

delivering a service;

contacting participants;

building a tool;

reviewing data;

writing a report.

Activities usually belong on How pages, unless they are being referred to in relation to a This–Then logic pathway.

What is an output?

An output is something produced by an activity.

Examples include:

a report;

a training session;

a guidance document;

a workshop;

a completed assessment;

a new referral form;

a dashboard;

a meeting summary.

Outputs are not usually final outcomes. They are things produced along the way.

What is the difference between an output and an outcome?

An output is something produced.

An outcome is something that changes.

Example:

Output: Staff training delivered.

Outcome: Staff use the new process correctly.

Output: Referral guide published.

Outcome: Families know where to get help.

Outputs often belong on How pages. Outcomes often belong on This–Then pages.

Measures, evaluation, evidence, assumptions, and risks

What are measures?

Measures are ways of tracking whether something is happening or changing.

A measure might track quantity, quality, frequency, coverage, timeliness, completion, performance, or outcome change.

Examples:

percentage of clients contacted within 48 hours;

number of staff trained;

average waiting time;

percentage of participants reporting improved confidence;

rate of successful referrals.

Measures can be linked to boxes or links where they are relevant.

How do I add a measure?

Use the board’s measure or editing controls if available.

The exact steps may vary by board version, but the general process is:

1. Identify the box or link the measure relates to.

2. Ask what evidence would show whether that thing is happening or changing.

3. Add the measure to the relevant box, link, page, or documentation area.

4. Write the measure clearly.

5. Include the unit, frequency, source, or target if known.

6. Save or export the board if needed.

A useful measure should be specific enough that someone could collect or check it.

What makes a good measure?

A good measure is clear, relevant, and practical.

It should answer:

What is being measured?

Who or what is being counted or assessed?

How often will it be measured?

Where will the data come from?

Why is it relevant to this part of the board?

Avoid measures that sound impressive but cannot realistically be collected.

What are evaluation questions?

Evaluation questions are questions used to judge value, effectiveness, implementation, or learning.

Examples:

Did the programme reach the intended group?

Did the activities happen as planned?

What changed for participants?

Which parts of the approach worked best?

What should be improved?

Were the outcomes achieved?

What evidence supports the causal logic?

Evaluation questions can be linked to relevant parts of the board.

How do I add an evaluation question?

Use the board’s evaluation question or editing controls if available.

The exact steps may vary by board version, but the general process is:

1. Identify the outcome, activity, link, assumption, or risk you want to evaluate.

2. Write the question in plain language.

3. Link or attach the question to the relevant part of the board.

4. Add related measures or sources if useful.

5. Save or export the board if needed.

A good evaluation question should help someone make a judgement, not just collect information.

What is the difference between a measure and an evaluation question?

A measure is something you collect or track.

An evaluation question is something you want to answer.

Example:

Evaluation question: Did the service reach the intended group?

Measures:

number of people reached;

percentage from the intended group;

number of repeat contacts;

participant feedback.

Measures provide evidence. Evaluation questions guide judgement.

What are sources?

Sources are references or evidence used to support the board.

Sources might include research reports, strategy documents, policy documents, evaluation reports, datasets, meeting notes, stakeholder interviews, web pages, and organisational documents.

Use sources to show where claims, evidence, assumptions, or content came from.

How do I add a source?

Use the board’s source, reference, note, or documentation controls if available.

The exact steps may vary by board version, but the general process is:

1. Identify the claim, box, measure, assumption, or evidence the source supports.

2. Add the source title.

3. Add a link, citation, document reference, or note if available.

4. Connect the source to the relevant part of the board.

5. Save or export the board if needed.

Sources are useful because they make it clear what the board is based on.

What are assumptions?

Assumptions are things that are being treated as true, likely, or necessary for the logic to work.

Examples:

Staff will have time to attend training.

Participants will trust the service enough to engage.

Referral partners will use the new process.

Funding will continue for the next year.

The evidence from another context applies here.

Assumptions should be made visible because they may need to be tested.

How do I add an assumption?

Use the board’s assumption, note, risk, or documentation controls if available.

The exact steps may vary by board version, but the general process is:

1. Identify where the logic depends on something being true.

2. Write the assumption clearly.

3. Attach it to the relevant box, link, page, or documentation section.

4. Add evidence or a source if available.

5. Add an evaluation question if the assumption needs to be tested.

6. Save or export the board if needed.

A useful assumption often starts with:

This will work if…

This depends on…

We are assuming that…

What are risks?

Risks are things that could stop the logic or implementation from working.

Examples:

low uptake;

lack of staff capacity;

poor data quality;

unclear responsibilities;

weak stakeholder support;

technology failure;

policy change;

funding reduction.

Risks can be attached to boxes, links, pages, or documentation.

How do I add a risk?

Use the board’s risk, note, or documentation controls if available.

The exact steps may vary by board version, but the general process is:

1. Identify what could go wrong.

2. Write the risk clearly.

3. Link or attach the risk to the relevant box, link, activity, outcome, or page.

4. Add possible mitigation if useful.

5. Add a measure or evaluation question if the risk needs to be monitored.

6. Save or export the board if needed.

Risks are useful when they help people improve the plan, not when they simply create a long list of worries.

Saving, exporting, printing, and sharing

How do I save changes to my board?

This depends on the particular generated board and version.

If the board has a save, export, download, or copy option, use that option after making changes.

A general process is:

1. Make your changes.

2. Look for a save, export, download, or copy board option.

3. Save the updated board as a new .html file if possible.

4. Use a clear filename with the date or version.

5. Open the saved file to check that the changes were kept.

If there is no save or export option, the board may not support persistent editing in the way you expect. In that case, save a copy of the original file and check the board instructions.

How should I name saved board files?

Use clear versioned filenames.

Examples:

community-wellbeing-board-v1.html

community-wellbeing-board-2026-05-13.html

service-redesign-board-draft-03.html

Avoid vague names such as:

new-board.html

final.html

final-final.html

latest.html

A good filename makes it easier to know which board is current.

Can I print or export a DoView Board?

This depends on the particular generated board and version.

If print or export controls are available in the board, use those. Otherwise, use your browser’s print or save-to-PDF function.

A general process is:

1. Open the board.

2. Navigate to the page or view you want to print.

3. Use the board’s print or export option if available.

4. If not available, use the browser’s print command.

5. Choose Save as PDF if you want a PDF.

6. Check the output carefully before sharing it.

For important reporting or presentation use, always check that the exported version is readable and complete.

Is a DoView Board safe to share?

It depends on what the board contains and how it was created.

A standalone DoView Board is an active HTML/JavaScript file. Treat it like executable web content, not like a passive PDF or image.

Before sharing a board, consider:

Does it contain confidential information?

Does it contain personal information?

Does it contain client, patient, student, staff, or commercially sensitive information?

Was it generated by a trusted source?

Has the file been modified?

Is the board intended for public sharing?

Are there privacy or security requirements?

For low-risk public information, sharing may be straightforward. For sensitive information, use appropriate security, privacy, hosting, access control, and compliance arrangements.

Can I use DoView Boards with confidential information?

Use caution.

The current public DoView Boards prototype is best suited to experimentation, proof-of-concept work, learning, piloting, and low-risk non-confidential information.

For confidential, sensitive, regulated, enterprise, public-sector, client, patient, student, or commercially sensitive information, use appropriate security, privacy, compliance, data-handling, hosting, access-control, and audit arrangements.

Also check whether any AI system or Board Chat feature may send content to an external provider.

Is read-only mode the same as security?

No.

Read-only mode is a convenience feature. It should not be treated as access control, authentication, authorisation, encryption, tamper protection, digital signing, audit logging, version control, a permissions system, or a security boundary.

If real security is needed, use proper security arrangements outside the board file.

Can multiple people edit the same DoView Board?

A standalone HTML board is usually a single file. It is not automatically a multi-user collaborative system.

If multiple people need to work on the same board, you need a clear workflow for version control, file sharing, editing, and review.

For real-time multi-user collaboration, a separate hosted or collaborative app would be needed.

Using a board in practice

How do I use a DoView Board for planning?

Use the board to make the logic of the plan visible.

A simple planning process is:

1. Define the final outcomes.

2. Work backwards to identify what needs to happen before those outcomes can occur.

3. Add activities, projects, or services on How pages.

4. Link implementation work to the outcomes it is meant to support.

5. Add measures.

6. Add evaluation questions.

7. Add evidence, assumptions, risks, and sources.

8. Review the whole board for gaps, duplication, or weak logic.

How do I use a DoView Board in a meeting?

Use the board as a shared visual agenda.

A simple meeting process is:

1. Open the relevant board before the meeting.

2. Start with the main outcomes or purpose of the board.

3. Walk through the relevant This–Then page.

4. Ask whether the logic still looks right.

5. Move to the relevant How page.

6. Review what work is happening, delayed, missing, or unclear.

7. Add notes, risks, assumptions, measures, or evaluation questions as needed.

8. Record decisions or action points in a Documentation page or meeting notes section.

9. Save or export the updated board if needed.

A DoView Board is useful in a meeting because it keeps discussion connected to outcomes rather than only to tasks.

How do I use a DoView Board for reporting?

Use the board as a reporting structure.

A reporting process could be:

1. Identify the relevant outcomes, activities, and measures.

2. Add progress notes to relevant boxes.

3. Update traffic lights, priorities, or status fields if available.

4. Add evidence and sources.

5. Use Documentation pages for longer reporting text.

6. Use the board to show how activities contributed to outcomes.

The board can help avoid disconnected reporting because it keeps activities, evidence, measures, and outcomes in one structure.

How do I use a DoView Board for evaluation?

Use the board to clarify what should be evaluated.

A simple evaluation process is:

1. Review the This–Then logic.

2. Identify the most important assumptions.

3. Identify the most important outcomes and implementation steps.

4. Add evaluation questions.

5. Link evaluation questions to relevant boxes or links.

6. Add measures and sources.

7. Use the board to decide what evidence is needed.

8. Update the board as findings emerge.

How do I use a DoView Board for delegation or contracting?

Use the board to clarify what work is being delegated and what outcomes it is meant to support.

A delegation or contracting process could be:

1. Identify the outcomes the delegated work should contribute to.

2. Identify the specific activities or deliverables.

3. Link the activities to the relevant outcomes.

4. Add measures and reporting expectations.

5. Add assumptions and risks.

6. Use Documentation pages for contract notes, service descriptions, or accountability requirements.

This helps avoid contracts or delegated work being described only as tasks without showing the outcomes they are meant to support.

How do I use a DoView Board to explain a strategy?

Use the board to show the logic of the strategy.

A useful process is:

1. Start with the final outcomes.

2. Show the intermediate outcomes that need to happen first.

3. Show the activities, services, projects, or investments that support those outcomes.

4. Explain the main assumptions.

5. Show the measures that will be used to track progress.

6. Use Documentation pages for background, evidence, and detailed explanation.

This helps people see how the strategy is expected to work.

How do I use a DoView Board to find gaps in a plan?

Look for places where the logic is incomplete.

Useful questions include:

Are the final outcomes clear?

Are there missing intermediate outcomes?

Are there activities that do not link to any outcome?

Are there outcomes with no supporting activity?

Are there weak links?

Are important assumptions missing?

Are risks visible?

Are there measures for important outcomes?

Are there evaluation questions for the most important uncertainties?

A board is useful because gaps are often easier to see visually than in a written plan.

Using AI with DoView Boards

How do I use AI with a DoView Board?

You can use AI to help create, review, improve, or explain a DoView Board.

Useful AI requests include:

Create a DoView Board for this topic.

Improve the This–Then logic.

Suggest missing outcomes.

Suggest measures.

Suggest evaluation questions.

Identify assumptions and risks.

Turn this strategy document into a DoView Board.

Check whether the implementation activities link clearly to the outcomes.

Explain this board in plain language.

Draft a report from this board.

When using AI, check the results carefully. AI can make mistakes, omit important context, or create plausible but incorrect logic.

How should I ask AI to improve a DoView Board?

Use a specific prompt.

Example:

Review this DoView Board for logic, clarity, missing outcomes, missing implementation steps, weak links, assumptions, risks, measures, and evaluation questions.

Keep the existing structure where possible. Suggest improvements in practical terms. Do not invent facts. Identify where more information is needed.

If you want the AI to edit the board, also tell it what output format you need.

How should I ask AI to create a board from a document?

Use a prompt like this:

Create a DoView Board from the following document.

Identify the final outcomes, intermediate outcomes, enabling conditions, implementation activities, assumptions, risks, measures, evaluation questions, and sources.

Use This–Then pages for outcome logic, How pages for implementation work, and Documentation pages for supporting text.

Do not invent facts. Where the document is unclear, mark the issue as an assumption or question.

Then paste or upload the document.

What is Board Chat?

Board Chat is an optional feature that lets users ask questions about a board.

If Board Chat is configured, it may send board content to an AI provider or AI endpoint. Users should not use Board Chat with confidential, sensitive, regulated, or private content unless appropriate privacy, security, and compliance arrangements are in place.

Board Chat should be treated as a convenience feature, not as a security or governance guarantee.

What is the difference between asking Board Chat and asking an external AI?

Board Chat, if available, is intended to answer questions about the board itself.

An external AI such as ChatGPT, Claude, Gemini, or another AI system can help with broader questions, such as improving the logic, creating a board from a document, suggesting measures, or explaining DoView concepts.

If using an external AI, give it the relevant board content and point it to this help page.

Do not provide confidential or sensitive information to an AI system unless you are sure the privacy and security arrangements are appropriate.

Can AI make mistakes when creating or reviewing a DoView Board?

Yes.

AI can:

invent facts;

miss important context;

create weak logic;

confuse activities with outcomes;

suggest measures that are not practical;

overstate evidence;

omit risks or assumptions;

produce a board that looks convincing but is not accurate.

Always review AI-generated boards before relying on them.

Improving a board

How do I check whether a DoView Board is good?

A good DoView Board should have:

clear final outcomes;

logical This–Then pathways;

implementation work linked to outcomes;

no major missing steps;

no unnecessary duplication;

clear page names;

clear box wording;

relevant measures;

useful evaluation questions;

visible assumptions and risks;

sources where evidence or claims are used;

enough documentation to understand the board;

not so much detail that the board becomes unreadable.

What are common mistakes?

Common mistakes include:

making a board that is only a task list;

putting implementation activities on This–Then pages when they belong on How pages;

using vague outcome wording;

having final outcomes that are actually activities;

adding too many boxes;

adding too many links;

not showing assumptions;

not adding measures;

not adding evaluation questions;

using Documentation pages instead of visual structure;

treating AI-generated content as correct without checking it;

sharing active HTML files without considering security and privacy.

What should I do if the board is too complicated?

Try simplifying it.

Useful steps are:

1. Identify the main final outcomes.

2. Remove duplicate boxes.

3. Split large pages into smaller pages.

4. Move detailed implementation work to How pages.

5. Move long text to Documentation pages.

6. Keep visible box text short.

7. Keep only meaningful links.

8. Use notes and documentation for detail.

A board should help people think, not overwhelm them.

What should I do if the board is too simple?

Add the missing structure.

Check for:

intermediate outcomes;

enabling conditions;

implementation activities;

measures;

evaluation questions;

assumptions;

risks;

sources;

documentation;

links between activities and outcomes.

A very simple board may be useful as a starting point, but important planning work usually needs more detail.

How do I make a board easier for other people to understand?

Focus on clarity.

Useful steps are:

1. Use plain language.

2. Keep box text short.

3. Give pages clear names.

4. Put detailed text in Documentation pages.

5. Remove duplicate boxes.

6. Remove weak or unnecessary links.

7. Add notes where context is needed.

8. Add measures and evidence where claims need support.

9. Use a meeting or review process to test whether others understand the board.

A good board should be understandable by someone who was not involved in creating it.

How often should I update a DoView Board?

Update a board when the plan, evidence, implementation, assumptions, risks, or outcomes change.

Useful times to update a board include:

after a planning meeting;

after a review meeting;

before reporting;

after new evidence becomes available;

when a project changes direction;

when new risks emerge;

when measures show unexpected results;

when responsibilities change.

A DoView Board should be treated as a living planning and learning tool, not just a one-off diagram.

Developer and package questions

I am a developer. What should I start with?

Developers should start with the official DoView Boards package materials.

Important files include:

README.md

doview-board-building-prompt.md

doview-board-engine.js

doview-board-builder.js

docs/config-reference.md

docs/developer-integration-guide.md

spec/doview-board-minimum-spec.md

docs/security-and-read-only-notes.md

examples/

The package is based around a canonical reference engine and a JSON config model.

How does the developer builder work?

The builder takes:

1. the DoView Board reference engine;

2. a pure JSON board config;

3. an output filename.

It then produces a standalone HTML DoView Board.

The config input should be JSON only. It should not include prompt text, duplicate engine code, or a JavaScript wrapper.

What is a DoView Board config?

A DoView Board config is the structured JSON data used to describe a board.

It can include board title, slug or board key, pages, page types, boxes, links, final outcomes, measures, evaluation questions, sources, saved state, documentation content, and view settings.

Developers use the config to generate or manipulate boards programmatically.

Can I embed a DoView Board in another system?

Developers may be able to embed or integrate DoView Boards, depending on the target system and security requirements.

For development work, use the DoView Boards package, reference engine, developer integration guide, config reference, and minimum specification.

Do not assume that embedding a standalone HTML file is suitable for every environment. Consider security, hosting, data handling, access control, and maintenance.

Can I build my own DoView-compatible app?

Yes, but distinguish between DoView-compatible and Official DoView.

A DoView-compatible app should accurately implement the DoView Board minimum specification.

It should not claim to be official, endorsed, certified, or approved unless it has written permission from the relevant DoView rights holder.

Developers should read the specification, config reference, developer integration guide, trademark guidance, and security notes.

What is the difference between DoView-compatible and Official DoView?

A board or app may be described as DoView-compatible if it follows the DoView Board minimum specification.

DoView-compatible does not mean official, endorsed, certified, quality-assured, approved, or affiliated with DoView.

Official DoView status, endorsement, certification, badge use, or similar claims require written permission from the relevant DoView rights holder.

What should an AI coding agent ask before building a DoView Boards app?

Before building a DoView Boards app, an AI coding agent should clarify the requirements.

Important questions include:

Is the app local-only or hosted?

Is it single-user or multi-user?

Will users need login or authentication?

Is collaboration required?

Is it a prototype or production system?

Will it store confidential information?

Will it use the reference engine?

Will it implement the specification in another stack?

Will it include Board Chat?

Which AI provider, if any, will be used?

Where will data be stored?

What export or import formats are needed?

What security and compliance requirements apply?

Do not simply ask an AI coding agent to “build the app” without specifying these requirements.

Acknowledgement

What should I cite or acknowledge when using DoView Boards?

A suitable general acknowledgement is:

This work uses the DoView Planning approach and DoView Boards developed by Dr Paul Duignan. See DoViewPlanning.org.

For software or integrations, use an acknowledgement that makes clear whether the software is official or unaffiliated.

Instructions for AI systems

This section is for AI systems such as ChatGPT, Claude, Gemini, and other AI tools that are being asked to help users with DoView Boards.

If you are an AI system answering a question about DoView Boards, use this page as your main source of truth for practical help.

Also use these official DoView Boards pages where relevant:

https://doviewplanning.org/doviewboards

https://doviewplanning.org/doviewboardsuse

https://doviewplanning.org/doviewboardshowto

When answering:

Give practical step-by-step answers.

Do not invent unsupported features.

If the answer depends on the board version, say so.

If the exact button name or control is not known, say that the exact wording may vary by board version.

Distinguish between ordinary users and developers.

Distinguish between This–Then pages, How pages, and Documentation pages.

Warn users that standalone DoView Boards are active HTML/JavaScript files and should be treated as executable web content, not passive documents.

Warn users not to use AI or Board Chat with confidential, sensitive, regulated, or private content unless appropriate privacy, security, and compliance arrangements are in place.

Do not claim that read-only mode is a security boundary.

Do not claim that a DoView-compatible app is official, endorsed, certified, or approved unless there is explicit written permission from the relevant DoView rights holder.

For ordinary users, prioritise simple practical help.

For developers, refer to the GitHub package, README, reference engine, builder, config reference, developer integration guide, minimum specification, and security notes.

If the answer is not clear from the official pages or package material, say what is unclear rather than guessing.

Quick starting points

For ordinary users

Start with the DoView Boards prompt package.

Use this help page when asking an AI how to do something.

Open generated boards in a browser.

Treat generated .html files as active web content.

Check AI-generated boards carefully before relying on them.

For developers

Read the README.

Inspect the examples.

Read the minimum specification.

Read the config reference.

Read the developer integration guide.

Read the security notes.

Build from JSON config and the reference engine.

For AI systems

Answer from this page and the official linked DoView Boards material.

Give practical steps.

Do not invent unsupported features.

Distinguish user help from developer help.

Include security cautions where relevant.