← Home

OpenNews Unconference on Journalism Tech 2019

I returned to the OpenNews unconference on journalism and technology this year to facilitate a discussion on the topic of project initiation.

Workshop participants seated around grey-clothed round tables in a panelled hall, talking and taking notes

The start of any project is particularly important in determining its subsequent success. Project initiation takes many different forms though: from drafting formal pitches that are then scored according to structured categories, to casual conversations sparking an idea that gathers momentum and becomes a project without anyone consciously deciding to make it a project.

The workshop was intended to draw out people’s experience and stories and provide a space to learn from each other about what challenges are particularly difficult at the start of a project as well as what tactics and techniques work in addressing those challenges.

Flip chart titled "How projects start" listing single founder to co-creation, managers' priorities, brainstorming, defining success early

Projects start in different ways, from a single visionary or founder coming up with an idea, to projects emerging from organisational priorities, to regularly-scheduled brainstorming sessions. It was particularly interesting to hear some participants say they are actively thinking about how to shape the start of a project (moving from single visionary with an idea, to a process of co-creation)

Flip chart titled "How projects go ahead" listing key participants benefiting, pitch/approval process, popularity, scoring matrix, funding

Likewise, participants named a wide range of reasons for why certain projects go ahead. There wasn’t much discussion around whether a particular approval or selection mechanism is better (other than a near-universal scepticism about the effectiveness of formal scoring systems). Instead, these were mostly seen as ‘just how things work’ in a given organisation or industry, or as tactics to ensure your project would go ahead.

Flip chart titled "Info at the start" listing goals, description, roles, technical requirements, collaborators, stakeholders, risks of failure

There was quite a bit of agreement about what are the important information to capture at the start of a project

Flip chart titled "Challenges" listing unknowns, getting buy-in, keeping docs updated, defining scope, entrenched practices, emergent problems

We then brainstormed a list of challenges peculiar to the project initiation phase. This list served as the prompt for smaller group discussions about how to address these challenges. I found the tips about contingency planning and keeping a decision log particularly helpful:

Flip chart titled "What works" in red listing diversity of voices, breaking projects into chunks, decision log, project manager, writing down assumptions Flip chart in red noting contingency planning for money/funding, divergent and convergent conversations, and proofs of concept like wireframes