Sitemap
Follow a branch. Open a heading to see what sits beneath it.
Numbers count the next branches shown in this map. 0 marks a leaf here, not an empty page.
Agent welcome
Lawrence Rowland explores project work through small scenarios, executable models, diagrams and source-backed explanations. This guide helps people and agents find their way through the published collection.
Home offers two entrances.
- Experiments: An entrance to Experiments, Scenarios and Working views: three ways into the same exploratory work.
- Library: Reusable methods, bounded worked examples and earlier material, organised by subject.
The Experiments landing page offers three routes, in this order:
- Experiments: Open enquiries and exploratory collections, each with its own question and scope.
- Scenarios: Familiar situations, each linking to the enquiries that use it. A scenario can support more than one method.
- Working views: The nets, maps, matrices and screens used inside the examples.
Four persistent navigation shortcuts remain available: Experiments opens this landing page; Library, Scenarios and Working views open their respective collections.
Each project keeps its own question, scope and account of what its examples establish. An essay here is a trial; a useful result may be a limitation or a failed attempt. Scenarios help people think; future enquiries may change their setting or method. This guide describes the collection and leaves research direction with each project.
12 scenarios connect settings to their enquiries. Working views shows the representations used inside the examples.
Read as Markdown · Detailed directory · Visual descriptions
Projects: questions, scenarios and limits (19)
The names, questions, scenarios and approaches follow the public project catalogue. These short boundary notes help interpret it; follow the project's own public scope when reading or continuing an enquiry. The linked End, Ways and Means statements belong to those projects.
SMC means symmetric monoidal category; WBS means work breakdown structure. Each example explains how, and how far, it uses its named methods.
| Project | Question | Scenario | Concepts | Scope, limits and sources |
|---|---|---|---|---|
| Gimmer: processes to plans | Which plans are allowed by the way the work actually happens? Lawrence’s main Petri → SMC → WBS collection: related models, generators and explanations, including earlier experiments. | Build a small refuge halfway up a cliff. | processes, WBS, schedule | Several process-to-plan constructions share this collection. Their assumptions and coverage differ; read the chosen construction's method and checks. GitHub source (may require access) |
| Integrated risks & tasks | Can tasks and threats be understood through one process model? Cows, concrete and shared access: compare original sketches, corrected wiring, process sets and alternative executions of a small resource model. | Pour the foundations before the cows take the lane. | processes, risk, composition, category theory | Toy resource rules, not a probability forecast or a real schedule. GitHub source (may require access) |
| Project Co-design | Can a feasible finished system be delivered through acceptable stages? Four wildlife-crossing essais: compose a complete crossing, construct a delivery path, compare programmes and size remote monitoring power. | Reconnect two habitats across a busy road. | co design, trade offs, staging, category theory | Synthetic capacities and costs; the model does not predict animal use. GitHub source (may require access) |
| Bricklaying a Rotunda | How can we explore changing project states? A collection of experiments around project dynamics, lenses and trajectories. | Build a circular brick wall, course by course. | dynamics, models, category theory | An exploratory collection of dynamics, lenses and trajectories; the chosen model's assumptions define what its paths mean. GitHub source (may require access) |
| Local to Global | When do local project views fit together? Two lines of enquiry: early Tangled Triangle sketches ask how AI interprets interfaces, topology and system architecture; later experiments test local-to-global consistency. | Fit a control centre onto the Tangled Triangle. | consistency, WBS, category theory | Early AI interpretations and later consistency checks are distinct lines of enquiry. A local-to-global result is tied to its stated model. GitHub source (may require access) |
| Shared waters: open systems | What do open-system methods help us understand about useful project chunks? Three corrected first attempts from the original GraphML sketches: boundary composition, organisational comparison, and explicit shared observations and capacity. | Connect an offshore depot, a power barge and their organisations. | open systems, composition, dynamics, category theory | First constructions of boundaries, organisations and shared observations; their computed results concern the supplied examples. GitHub source (may require access) |
| Programme Decision Sequences | How should a programme act as uncertainty unfolds? Models, worksheets, worked paths and IT decision games for acting under uncertainty. The experiments catalogue distinguishes live simulations, tutorials and historical reports. | Choose now; learn more before the next decision. | decisions, uncertainty, programmes | The collection distinguishes simulations, tutorials and historical reports. For example, its finite evidence model uses invented payoffs rather than forecasts. GitHub source (may require access) |
| Gimmer: higher-autonomy experiments | Can work packages share resources without hiding valid ways to build? A parallel Petri → SMC → WBS investigation. Agents choose bounded next steps and repeat build, test and review loops as compute permits. | The same refuge, with the awkward handovers left in. | processes, WBS, higher autonomy | Exactness depends on the declared finite object and completed search. Illustrative durations are not verified construction methods. GitHub source (may require access) Public scope and method boundaries |
| Project Spines | What can schedule structure reveal beyond dates? Six tabs on schedule spines, antichain slices, finite shed construction, review loops, vacillation boundaries and project-controls interpretation. | Build a mountain-refuge shed, one dependency at a time. | schedule, project controls, posets, antichains | Precedence structure and partition results do not by themselves establish a resource-feasible schedule. GitHub source (may require access) |
| Functors for Projects | How might mathematical structures illuminate project work? Browse experiments in functors, adjoints, sheaves, wiring diagrams and finite colimits, including the grounded-theory coding illustration. | Describe one project in more than one useful way. | category theory, models, project management | An exploratory collection, not one bounded foray or a complete project-management system. Each construction has its own mathematical and practical limits. GitHub source (may require access) Collection purpose and limits (3 October 2026 copy) |
| Building a Wall | Can explicit interfaces turn project work into reusable blocks? Project wiring diagrams, beginning with a construction essay on readiness, reusable modules and computed checks, alongside eight earlier explorations. | Build a wall that is ready to receive a roof. | wiring diagrams, composition, readiness, category theory | Readiness and interface checks concern the declared construction; they are not evidence of a completed real build. GitHub source (may require access) |
| Gimmer: broader collection | What else must we understand beyond a task list and dates? Observation, binding, procurement, ontology and change experiments outside the Petri → SMC → WBS collection and higher-autonomy work. | Deliver the refuge—and keep its different accounts connected. | observation, procurement, ontology, change | A collection of different project questions, not one uniform planning model. Read the scope of the selected essay or app. GitHub source (may require access) |
| Solway Tunnel Ontology | How can a project ontology connect to a plan? Ontology and WBS experiments using a tunnel scenario, with a separate knowledge-graph audit. | Imagine delivering a tunnel beneath the Solway. | ontology, WBS, knowledge graphs | An ontology, a WBS and a knowledge-graph audit answer different questions; none alone establishes tunnel feasibility. GitHub source (may require access) |
| Portfolio Wave reading map | How do sources, themes and projects connect? Explore the public source–project–topic projection through the Portfolio Wave view of the concepts graph. | Follow a reading idea into a project experiment. | knowledge graphs, sources, projects | A public source–project–topic projection. A link suggests a reading connection, not proof that the source establishes a project's claims. GitHub source (may require access) |
| Tag Concurrence Graph | Which concepts occur together in reading and app collections? Concepts-graph views for reading collections and a dated React app-catalogue tag map, with explicit source and refresh information. | Find connections in a shelf of tagged reading. | knowledge graphs, sources | Co-occurrence maps describe the indexed collection and its refresh state; an association is not a causal or semantic proof. GitHub source (may require access) |
| Knowing enough to act together | What must each crew know to choose its part of the move? Compare route cues, completion reports and direct inspections. Discover which information arrangements let the handlers choose a passage and the curator decide whether to reopen. | Move an oversized whale exhibit through a museum. | knowledge, coordination, project state | The museum scene is provisional. Finite checks distinguish local choice from physical possibility; they do not settle the wider enquiry or demonstrate human benefit. GitHub source (may require access) Public End, Ways and Means |
| Meta Project Innovation | Could we improve the project before optimising its plan? Frontier Lab explores five independent lenses on one case. Demand challenge and evidence sensors connect to this foray's original candidates; their combined practical value remains open. | Move customer data to the cloud, questioning the inherited scope. | project management, planning, evidence, innovation | Frontier Lab is one early trial of five planning lenses; it does not define the wider foray. Their combined practical value remains open. GitHub source (may require access) |
| Counterfactual programme steering | What would change if we chose a different management policy? Project Causal Lab pairs a causal-graph explorer with a separate programme-policy model. An early Counterfactuals trial, with the boundary between assumptions, fitted data and causal evidence made explicit. | A delivery team considers more automation, extra staff or a lower WIP limit. | causality, counterfactuals, decisions, simulation | A causal-graph explorer and a separate policy model. Supplied assumptions, fitted data and causal evidence must remain distinct. GitHub source (may require access) |
| Bracken Vale: useful project interventions | Which small interventions help project people see and do something useful? Practical trials explore project decisions, relationships, measures and evidence-linked drafts in a fictional railway. Inputs and results stay inspectable; practical human benefit remains to be tested. | A small railway has renewals to plan, decisions waiting and several accounts of what matters. | project management, decisions, evidence, relationships | Fictional project trials with inspectable inputs and results. First-version coverage does not establish adoption or practical human benefit. GitHub source (may require access) Public End, Ways and Means (3 October 2026 copy) |
Library subjects and evidence boundaries
Library placement means a reusable or more established example has a home; it does not certify the method. A model check, a working interface, mathematical proof and demonstrated human benefit are different kinds of evidence. Read the selected example's assumptions, source uses and limits.
- Project states & relationships — Connect tasks, states, people and resources. Explore shared project models, process diagrams and the relationships behind a portfolio. (18 entries)
- Decisions & trade-offs — Frame a decision, compare competing objectives, and inspect what buffer, delay assumptions and new information change. (14 entries)
- Delivery dynamics & feedback — Explore dependency loops, learning, rework, reviews and site occupancy through deliberately small models. (14 entries)
- Data, evidence & assurance — Match methods to the available information. Examine data maturity, project controls and what earlier prediction experiments could establish. (13 entries)
- Capabilities & futures — Explore the practices, capabilities and tools a portfolio might need, with earlier reading, framework guides and clearly labelled future scenarios. (16 entries)
- Custom GPTs — coaches, co-pilots and agents for thinking through project work.
Further shelves: Wider interest · Sitemap. Wider interest has 8 pictured entries.
Reading the pictures (111 views)
Working views collects the nets, maps, matrices and screens used inside the examples, rather than project emblems or scene illustrations. Read the caption, depicted state and limitation before opening the example. A screenshot records one view; it does not prove the model’s claims or show its current state. Text descriptions and source links remain available when pictures or interaction are unavailable.
Hover or focus for a hint; open a picture for its caption, “Look for”, “Keep in mind” and “View shown”. The preview links to the full image and its original example. Read all visual descriptions in Markdown.
Experiments 3
Experiments 19
19 enquiries and collections
- Gimmer: processes to plans 16
16 example entrances
Sixteen numbered apps in the Processes to plans catalogue. Repeated featured links count once.
- Project process and task explorer 0
- WBS via PDDL 0
- Processes to plans: shed on a cliff 0
- Build-a-shed mini-generator 0
- Petri net to WBS to schedule 0
- Processes to plans: halfway up a cliff 0
- Cliff shed event structure 0
- Mountain shed WBS from a Petri net 0
- Process-first project model 0
- Petri net checks 0
- Build a shed with split materials 0
- Cliff refuge mini-generator 0
- Composition of complex systems 0
- Generate refuge schedules from process rules 0
- Cliff refuge: Petri net to WBS 0
- Constraint-to-Plan Studio 0
- Integrated risks & tasks 1
1 example entrances
One essay and interactive lane model with several representations, not a separate app per section.
- Project Co-design 4
4 example entrances
Four separately modelled essays, with one distinct app per question.
- Bricklaying a Rotunda 7
7 example entrances
Seven maintained essay entrances. Companion sources and method pages are not additional experiments.
- Local to Global 8
8 example entrances
Seven later essays and one early-interpretation hub. The hub opens into six distinct variants; the two enquiry purposes remain separate.
- Early Tangled Triangle interpretations (six variants) 6
6 variants
- Regional Signalling Control Centre – Site Geometry & Topology (Concept Sketch) 0
- Tangled Triangle — Concept Geometry Sketch (Plan + Section) 0
- Tangled Triangle – Conceptual Plan & Section (Interactive) 0
- Regional Signalling Control Centre — Interface Topology Sketch (v0) 0
- Regional Signalling Control Centre – Concept Sketch & Architecture Options 0
- Regional Signalling Control Centre – Concept & Architecture (v0) 0
- Scope coherence 0
- Project director view 0
- Tangled Triangle compatibility 0
- A director’s primer 0
- Patch validator 0
- Blueprint mnemonic 0
- Navigation mnemonic 0
- Early Tangled Triangle interpretations (six variants) 6
- Shared waters: open systems 3
3 example entrances
The three corrected first attempts, one page each.
- Programme Decision Sequences 8
8 example entrances
Eight catalogue entries, including the clearly labelled historical report and the original model on the home page.
- Gimmer: higher-autonomy experiments 8
8 example entrances
Six current labs and two explicitly earlier graph views. The inherited comparison in the broader Gimmer collection is not counted again.
- Project Spines 6
6 example entrances
Six named views reached by maintained tab fragments. Three are embedded standalone pages and three are native views.
- Functors for Projects 16
16 example entrances
Sixteen entries in the opening catalogue. This is an exploratory collection, not one bounded foray.
- The Island Reading Room: policies in conversation 0
- Milestones under changing constraints 0
- The atlas: ideas and explanations 0
- The atlas: explore a project graph 0
- Grounded theory and a finite colimit 0
- Three-way project relationships 0
- Currying: changing the shape of a mapping 0
- Products, coproducts, pullbacks and pushouts 0
- Presheaves and opposite categories 0
- Functors as objects 0
- Models and natural transformations 0
- Sheaf-style schedule playground 0
- Group actions for project thinking 0
- Galois adjoints 0
- Category theory construction toolkit 0
- Composable uncertainty wiring 0
- Building a Wall 11
11 example entrances
Eleven entries in the app catalogue linked from the head. The opening page itself features one of them.
- Wall-building wiring diagram (W) 0
- Wall wiring diagram (SMC/Operad) 0
- Construction as an Operad Algebra 0
- Wall + Roof Contracts Algebra 0
- SysML wiring comparison 0
- Build a house. Keep the interfaces honest. 0
- Cliff shed WBS dual view 0
- Processes ↔ Plans: Shed-on-a-Cliff 0
- Petri → SMC → WBS (Brick Wall) 0
- One diagram, several meanings 0
- How a course repeats 0
- Gimmer: broader collection 13
13 example entrances
Twelve primary apps plus the separately labelled comparison entrance to shared App 20. That comparison is not another implementation.
- Homotopic cliff shed construction 0
- Resource Heaps 0
- Half-cliff shed operations console 0
- Temporal binding approach 0
- Cliff shed binding prototype 0
- Active inference procurement 0
- Project binding experiments 0
- Mountain refuge change requests 0
- Why one plan can hide different process rules 0
- Gimmer Crag shed ontology explorer 0
- Project change requests 0
- Sheaf Change Control Workbench 0
- Sheafified Change Impact Workbench 0
- Solway Tunnel Ontology 14
14 example entrances
Thirteen app-catalogue entries plus the broader ontology route linked from the head. The opening page features four direct examples; this count includes the catalogue.
- The handover game 0
- push-out-pull-back 0
- tunnel-ontology-visualizer 0
- global-WBS-by-sheaf 0
- sheaf-wbs-prototype 0
- two-possible-means 0
- solway-firth-tunnel-fibration-demo 0
- solway-sheaf-wbs-prototype 0
- sheaves-for-tunnel-concept 0
- ontologized-allen-schedule 0
- kglab-ontology-audit 0
- The work that must exist 0
- Digital Construction ontology — early essai 0
- Explore the tunnel ontology 0
- Portfolio Wave reading map 1
1 example entrances
One live reading map. Outbound papers and forays are evidence and connections, not child apps.
- Tag Concurrence Graph 3
3 example entrances
Three reading or catalogue graph views. The separately listed Portfolio Wave reading map is not counted again.
- Knowing enough to act together 1
- Meta Project Innovation 1
1 example entrances
One Frontier Lab app with five internal modes. The modes do not have independently activated URL routes.
- Counterfactual programme steering 1
1 example entrances
One essay and app containing causal-path and policy-simulation modes. The two modes are not one fitted model.
- Bracken Vale: useful project interventions 33
33 example entrances
Thirty-two app cards and one narrative essay. These are named public entries, not thirty-three validated methods.
- Small interventions, useful questions — the essai 0
- Which account applies? 0
- Whose outcome? 0
- A connection has a kind 0
- The constraint moves 0
- A trial worth having 0
- A signal worth seeing 0
- Small enough to agree 0
- Keep the recipe 0
- What applies here? 0
- A route that fits 0
- A meeting with a decision 0
- Checked in what sense? 0
- Useful elsewhere? 0
- Learn from the case 0
- Ready on the first pass? 0
- The missing link 0
- A gate with reasons 0
- What is in the tables? 0
- Make retreat possible 0
- What did the task list miss? 0
- A draft is not a gate 0
- Try one office job 0
- Keep the disagreement 0
- Remember before deciding 0
- Find the story in the pattern 0
- The work of getting better 0
- Practise on the artefact 0
- What does that number mean? 0
- Know now, act later? 0
- The shape of waiting 0
- Spend attention carefully 0
- The shared dependency 0
Named entrances from each opening page or its linked catalogue. The counts do not rank their maturity or claim completeness.
Scenarios 12
12 scenarios
- Gimmer refuge 5
5 enquiries in this setting
- The farm track 1
1 enquiries in this setting
- A wildlife crossing 4
4 enquiries in this setting
- A brick rotunda 2
2 enquiries in this setting
- The Tangled Triangle 2
2 enquiries in this setting
- Shared waters 3
3 enquiries in this setting
- A wall and its roof 3
3 enquiries in this setting
- A tunnel beneath the Solway 1
1 enquiries in this setting
- Moving the museum whale 1
1 enquiries in this setting
- Bracken Vale railway 1
1 enquiries in this setting
- The mountain-festival shuttle 1
1 enquiries in this setting
- The Island Reading Room 1
1 enquiries in this setting
One familiar situation can support several different enquiries. Their example lists sit in the Experiments branch.
Working views 111
111 working views
- When can the next task start? 0
- Which chain crosses every work layer? 0
- Can all five local rules agree? 0
- Can evidence change the choice before it closes? 0
- When does an answer become the next question? 0
- Is a way of moving the same as a path? 0
- Find the feedback group 0
- Keep three kinds of thing distinct 0
- See a complete crossing choice 0
- Where does the scaffolding go next? 0
- Put the project inside its context 0
- What does one more buffer day buy? 0
- Join two modules at one handover 0
- Can everyone agree and still double-book the team? 0
- What must travel back across an interface? 0
- Compose two mobilisation processes 0
- Look at one project through fourteen views 0
- Do three pairwise links make a joint decision? 0
- Make competition for the lane visible 0
- Reconcile four directors’ views 0
- Which distinctions do your coding choices remove? 0
- Keep plans attached to their assumptions 0
- Separate doing from becoming true 0
- Collapse a feedback loop into one group 0
- See what abstraction forgets 0
- The plan before the cows 0
- Let an outside process into the plan 0
- Read joint work as a composed arrow 0
- Does more capacity remove the wait? 0
- Narrow the view and notice what disappears 0
- Connect strategy to delivery and operations 0
- See which branch has room to move 0
- Inspect an early task-to-token translation 0
- Connect software tools with possible data 0
- Read just the task chain 0
- Choose the practices a portfolio needs 0
- Turn project records into a question worth testing 0
- Decide now—or find out more first? 0
- Which work is enabled now? 0
- The same drawn endpoints, different paths 0
- What does task proximity actually mean? 0
- One history after a major revision 0
- Follow the particular wire 0
- Which capabilities are retained, extended or added? 0
- How widely do outcomes spread under one policy? 0
- A section makes one interpretation inspectable 0
- A calendar bucket can contain a hidden dependency 0
- Different arrows carry different obligations 0
- Which assumed arrow makes adjustment necessary? 0
- The finished crossing is only part of the promise 0
- Compare neighbourhoods without flattening relationships 0
- Follow an outcome back to its supporting work 0
- Keep filing, interpretation and source use distinct 0
- Which concepts occur together in the reading? 0
- Two rings, one reserved hoist 0
- The next course needs the wall’s memory 0
- Carry intervals through connected calculations 0
- An ontology separates kinds of project information 0
- Threats cut across intended work 0
- Possible in every case, but can the handler choose? 0
- One load connection, explicit conditions 0
- Outputs and hoped-for benefits 0
- A checklist still has gaps 0
- A decision record takes shape 0
- Moving along or beyond a frontier 0
- How two uncertainties move together 0
- Inspect a capability profile 0
- A slice of the project-tool timeline 0
- A severe risk in a moderate band 0
- Three options tie after a weight change 0
- Four tasks, four suggested responses 0
- Follow work into a product 0
- Empty regions in assumed capability scores 0
- A need, a service and intervention levels 0
- Influence and interest are different axes 0
- Give candidate work a primary home 0
- Trace a risk judgement into a choice 0
- Where can this state graph get stuck? 0
- When a review changes the next move 0
- Watch work, learning and debt move together 0
- Find the question behind a capability 0
- Trace a learning route through project controls 0
- Put decision times beside the work 0
- See which delay moves the finish 0
- Keep funding and milestone claims inspectable 0
- Inspect a changed task network 0
- Read what changed in a date estimate 0
- Follow a change across shared interfaces 0
- Inspect why a governance rule passes 0
- See why a record enters a project view 0
- Locate where the material waits 0
- Compare the schedules behind a trade-off 0
- Group records by their shared control tags 0
- Compare a contract’s links with its places 0
- Test a theme against its supporting text 0
- Does a dated schedule satisfy its qualitative rules? 0
- Who owns the shared enabling work? 0
- Which dependencies have only one source? 0
- What changes when this task is done? 0
- Which schedule does this token history support? 0
- Which extra rules did the stages invent? 0
- What must the response cover before the review arrives? 0
- Do the local plans agree on their shared tasks? 0
- Can either response meet both shared bounds? 0
- Who can distinguish a completed move? 0
- What is the least information work this brief needs? 0
- Is adapting worth the survey and the wait? 0
- Can the same brick count permit different next moves? 0
- Can we regroup without changing the behaviour? 0
- Do lanes and stages give the same composite? 0
- What is the difference between false and no allowed result? 0
The representations used inside the examples.
Library 8
8 collections and entrances
Project states & relationships 18
- How should the work fit into a shared picture? 0
- Move a project through a portfolio 0
- Contract Portfolio Board 0
- How do two mobilisation processes fit together? 0
- From shed states to a candidate task structure 0
- See a project from different seats 0
- Who needs a different conversation? 0
- How does railway scope connect to people and objectives? 0
- Read a stakeholder concept schema 0
- Following questions through a US IT portfolio 0
- Trace outputs towards benefits 0
- Follow work into products 0
- Olaf’s afternoon deliveries 0
- Graphs & connections 0
- Data models for project portfolios 0
- Social Debt 0
- Explore project states and possible traps 0
- Inspect what a graph change preserves 0
Decisions & trade-offs 14
- Reframe a two-sided question 0
- Find the kind of decision you are making 0
- Compare options with weighted criteria 0
- Find a better trade-off together 0
- What do your decision weights imply? 0
- Compare a backlog with its stated priorities 0
- What does another day of buffer buy? 0
- Decide now—or find out more first? 0
- Build and interpret a risk matrix 0
- When do task delays happen together? 0
- Sort tasks by urgency and importance 0
- Follow a decision through a project graph 0
- Explore a project agreement 0
- Rehearse a regulatory negotiation 0
Delivery dynamics & feedback 14
- Find the delay that moves the finish 0
- See what a plan rewrite changes 0
- A project review changes the next move 0
- Explore the assumptions behind a delivery date 0
- Trace decisions beside overlapping work 0
- Time Exchange 0
- Find the feedback groups. 0
- How changes spread between project interfaces 0
- A software team learns and reworks 0
- Waste-route capacity 0
- A day on the pool-and-gym site 0
- See when feedback settles or grows 0
- Trace dependencies across phases and time 0
- What makes concurrent change costly? 0
Data, evidence & assurance 13
- Which method fits the question and the available data? 0
- Discuss data maturity in context 0
- Check the shape and meaning of project data 0
- What could an activity-delay forecast know in time? 0
- Inspect a governance trail 0
- Scenario and control lattice 0
- Find your way into project controls 0
- Project graph views 0
- Turn project records into a question worth testing 0
- Applying appropriate machine-learning approach. 0
- Read a crossing project through its notices 0
- Reading claims from project text 0
- Read project health and benefit assumptions 0
Capabilities & futures 16
- Which working practices does this portfolio need? 0
- Separate capability, maturity and performance 0
- Project management: Some jobs to be done 0
- Review portfolio-office capabilities 0
- Build a more useful programme conversation 0
- Match a task to a capability 0
- Idea notebook 0
- Adopt existing portfolio framework 0
- Gap Map 0
- Explore gaps in a capability map 0
- Follow the changing project-tool landscape 0
- Imagine different project-services markets 0
- Books 0
- Deep Research 0
- Compare overlapping scenario pressures 0
- Shape a useful project service 0
- Custom GPTs 0
- Wider interest 8
- Sitemap 0