Morganable
Projects
Objective · Scope · Execution · Deliverables

A project should know what it is trying to change — and what completion means.

Morganable Projects organise bounded public-interest undertakings around defined objectives, evidence, execution, accountable deliverables and a clear relationship between completion and what should endure.

01 / Objective Define the change
02 / Scope Set the boundary
03 / Evidence Establish the basis
04 / Execute Do the work
05 / Deliver Produce the result
06 / Close Preserve what remains
01 / Definition
What A Morganable Project Is

A bounded institutional undertaking organised around a defined objective.

A Morganable Project exists to accomplish something identifiable: investigate a problem, construct an asset, deliver a defined body of work, establish infrastructure, recover evidence or execute another bounded institutional objective.

A project may contain journalism, research, datasets, technology, multimedia, analysis or other specialist work, but those components should remain connected to the defined project objective.

Unlike a programme, which may continue because its institutional mission remains consequential, a project should eventually reach a point at which its original undertaking can be assessed as completed, discontinued, transformed or transferred into an enduring asset.

The project ends when the undertaking is complete. Valuable knowledge does not have to end with it.
Work Architecture

Bounded work is different from sustained work.

Morganable distinguishes Projects from Programmes, Series and Observatories so that duration, accountability, evidence and completion remain intelligible.

01

Project

A bounded undertaking with a defined objective, execution path and completion condition.

Projects →
02

Programme

A sustained institutional mission capable of coordinating multiple projects and workstreams.

Programmes →
03

Series

A sequential body of journalism, research or analysis developed through multiple related outputs.

Series →
04

Observatory

A persistent monitoring system organised around repeated observation and longitudinal evidence.

Observatories →
Project Architecture

From objective to
accountable completion.

Good project architecture preserves the relationship between what was intended, what was permitted inside the scope, what evidence was required, what was delivered and what remained unfinished.

01

Objective

Define the problem, intervention or institutional result the project exists to address.

02

Scope

Establish what belongs inside the project and what explicitly remains outside it.

03

Evidence

Identify the data, research, reporting or other evidence required to execute responsibly.

04

Execute

Deliver the defined work through governed tasks, milestones and specialist contributions.

05

Deliver

Produce the agreed outputs, assets, findings, systems or other project results.

06

Close

Assess completion, record residual work and preserve any assets with continuing institutional value.

Project Charter

Every project should be able to explain why it exists.

Project architecture should make the undertaking sufficiently clear that progress and completion can later be judged against something more substantial than activity alone.

01 / Objective

Defined result

The project should state the problem, result or institutional objective it exists to address.

02 / Boundary

Controlled scope

Project boundaries should prevent unrelated work from silently expanding the undertaking.

03 / Evidence

Demonstrable basis

Significant decisions and claims should be supported by the level of evidence appropriate to the project.

04 / Completion

Discernible end condition

Completion should be capable of assessment against stated deliverables, milestones or acceptance criteria.

Scope Discipline

A strong project defines both what it will do and what it will not.

Scope boundaries protect quality by preventing uncontrolled expansion from consuming resources, obscuring responsibility or making completion impossible to define.

Inside Scope

Work required to satisfy the objective.

In-scope work should have an identifiable relationship with the project’s agreed undertaking and completion criteria.

  • Defined deliverables
  • Required evidence
  • Approved workstreams
  • Necessary technical components
  • Project-specific governance
  • Documented completion criteria
Outside Scope

Valuable work that does not belong inside this undertaking.

Excluding work does not imply that it lacks value. It means the work should be governed elsewhere rather than silently enlarging the current project.

  • Unrelated institutional objectives
  • Future-stage enhancements
  • Separate programmes
  • Independent projects
  • Unapproved feature expansion
  • Work without completion relevance
Project Lifecycle

Progress should describe movement toward completion, not simply activity.

A project lifecycle allows Morganable to distinguish an idea from a scoped undertaking, active execution from completion, and completion from preservation.

P / 01

Proposed

Objective and public-interest rationale identified.

P / 02

Scoped

Boundaries, deliverables, dependencies and approach defined.

P / 03

In Development

Infrastructure, evidence or preparatory work being built.

P / 04

Active

Core execution underway against the defined undertaking.

P / 05

Completed

Completion conditions and required deliverables satisfied.

P / 06

Preserved

Valuable residual assets retained for future use.

Project Portfolio

Bounded undertakings. Visible purpose. Governed status.

Morganable’s project gateway should progressively make individual projects discoverable as their public status, documentation and institutional positioning are ready.

Project / Culture & Knowledge Developing

African Heritage Atlas

A developing Morganable project designed to build structured knowledge around African heritage, historical memory, cultural identity and related public-interest evidence.

Explore Project
Portfolio / Governance Controlled

Additional Projects

Further project entries can be added to this portfolio as their public identity, lifecycle status and supporting project architecture are ready for publication.

View Work Architecture
Project Deliverables

Completion depends on what the project was built to deliver.

Project outputs vary according to the undertaking. A strong project should define appropriate deliverables rather than forcing every initiative into the same format.

01 / Research

Research Outputs

Papers, findings, evidence reviews or other structured research products.

02 / Data

Datasets

Governed data assets, registers, classifications and associated documentation.

03 / Public Record

Journalism

Reporting, explainers, investigations or other publication outputs arising from the work.

04 / Infrastructure

Systems & Tools

Technical or institutional infrastructure required to achieve the project objective.

05 / Knowledge

Archives & Registries

Structured records preserved because the project creates continuing knowledge value.

06 / Method

Methodologies

Reusable methods, standards, classifications or analytical procedures created during execution.

Project Governance

Execution should remain accountable to the undertaking.

Project governance protects scope, evidence, responsibilities, completion criteria and the integrity of the final result.

01
Objective before activity

Work should be judged by its relationship to the project objective rather than volume of activity.

02
Scope before expansion

Material additions should be governed rather than silently absorbed into the undertaking.

03
Evidence before completion claims

Project status should correspond to demonstrated deliverables and acceptance conditions.

04
Dependencies before certainty

External evidence, technology, permissions or institutional dependencies should remain visible.

05
Residual work before closure

Incomplete or deferred work should be recorded rather than concealed by a completion label.

06
Preservation before disposal

Valuable evidence, methods and assets should survive project closure where continuing utility exists.

Closure & Preservation

Completion should close the undertaking, not erase its value.

A completed project may leave behind evidence, methods, datasets, archives or systems that deserve a longer institutional life.

The project can end. The asset can endure.
Deliverables accepted Completion
Residual work recorded Transparency
Evidence preserved Provenance
Reusable assets identified Continuity
Ownership transferred Governance
Project state archived Memory
Project Status

A project should not appear complete before its evidence says so.

Morganable should distinguish project stages according to actual scope, execution and completion rather than treating every named initiative as fully operational.

01

Proposed

Objective and rationale identified but undertaking not yet fully scoped.

02

Scoped

Boundaries, deliverables and completion conditions defined.

03

In Development

Evidence, infrastructure or preparatory components being built.

04

Active

Core project execution is underway.

05

Completed

Required undertaking and completion criteria have been satisfied.

06

Preserved

Valuable project assets remain governed for continuing institutional use.

Connected Institutions

Projects can draw on Morganable’s wider institutional capabilities.

The project form provides the bounded execution layer, while specialist capabilities provide appropriate research, data, intelligence and knowledge infrastructure.

01 / Programmes

Programmes

A project may operate independently or deliver a bounded component within a sustained programme.

Explore Programmes →
02 / Research

Research

Projects can require structured inquiry, formal methods and evidence-led investigation.

Explore Research →
03 / Data

Data

Project execution can create datasets, registries and other reusable evidence assets.

Explore Data →
04 / Intelligence

Intelligence

Some projects may require monitoring, assessment or decision-relevant analysis.

Explore Intelligence →
05 / Knowledge

ÀṢÀ

Valuable project evidence and assets can become connected to deeper institutional knowledge structures.

Explore ÀṢÀ →
06 / Monitoring

Observatories

A bounded project may create infrastructure or evidence later used within persistent monitoring systems.

Explore Observatories →
Project Portfolio Status

Proposed, scoped, active, completed and preserved are different states.

Morganable’s project portfolio may contain initiatives at different stages of definition, evidence acquisition, development, execution and closure. Public descriptions should reflect demonstrated project status rather than anticipated completion or future scale.

Wider Work Architecture

Projects are one form within Morganable’s wider institutional portfolio.

Explore how Morganable distinguishes Projects from Programmes and Series and how those forms can connect.

Programmes · Projects · Series Different institutional objectives require different structures, durations and completion obligations.

The Programmes, Projects & Series gateway explains Morganable’s wider architecture for organising sustained, bounded and sequential work.

Explore Programmes, Projects & Series →
Morganable Projects

Define the objective.
Execute the work.
Preserve what remains valuable.

Morganable Projects are designed to turn defined public-interest objectives into accountable undertakings with controlled scope, evidence, execution, deliverables and a clear relationship between completion and enduring value.

Welcome Back!

Login to your account below

Retrieve your password

Please enter your username or email address to reset your password.

Add New Playlist

Facebook
Verified by MonsterInsights