Internal systems
I created internal systems supporting the organisation’s work. This is the part of the portfolio centred on software for internal users and business processes.
DETAILED WORK SHOWCASE / FAIR OBSERVER
Building the tools
behind editorial work.
As Founding Product Manager at Fair Observer, I created internal systems, mailing systems and an editing engine, and used Asana for project management.
- MY ROLE
- Founding Product Manager
- WORK SCOPE
- Internal systems · editing engine · mailing systems
- TOOLS / CONTEXT
- Asana for project management
ORGANISATIONInternal systems
Supporting the work behind the publication
EDITORIALEditing engine
A dedicated product area for editorial work
COMMUNICATIONMailing systems
Tools for the organisation’s mailing needs
PROJECT MANAGEMENTAsana
Used for project management at Fair Observer
01 / CONTEXTProduct work inside
Product work inside
an organisation.
At Fair Observer, I worked as Founding Product Manager and created tools for internal, editorial and mailing work.
This is the most direct product-management example in my portfolio. The work concerned systems used within an organisation, alongside project management in Asana.
My contribution
Created internal systems, mailing systems and an editing engine. Used Asana for project management.
02 / DELIVERED WORKThree systems.
Three systems.
Distinct work needs.
Editing engine
I created an editing engine. This provides a concrete product area for discussing editorial needs, how work is represented in a tool and the choices behind the implementation.
Mailing systems
I created mailing systems for Fair Observer. This is a separate work area around organisational email communication and the tools needed to support it.
The system overview illustrates the areas of work. It does not reproduce the production interfaces.
03 / ASANAManaging the work
Managing the work
with Asana.
AsanaUsed for project management
Used for project management
at Fair Observer.
Alongside building internal products, I used Asana to manage project work at Fair Observer. This gives me direct experience using the product in an organisational setting.
For a work-management product role, this is useful context: I bring both a system-builder’s perspective and experience as an Asana user. The implementation story can connect what was being built with how its project work was managed.
04 / PRODUCT RELEVANCEThe connection
The connection
to B2B software.
These projects are relevant to B2B product teams because they concern tools for people doing recurring organisational work. The product lens below explains that connection.
| EXPERIENCE | PRODUCT CONNECTION |
|---|---|
| Internal systems | Internal tools and business workflow software. |
| Editing engine | A tool designed around a specific professional work context. |
| Mailing systems | Organisational communication and recurring operational work. |
| Asana project management | Direct use of work-management software in a product role. |
PRODUCT DISCUSSIONWhat makes a tool useful
What makes a tool useful
inside a team?
The useful questions are about the work it supports: who uses it, what they need to accomplish, where friction appears and what evidence shows that the system helps. These are the questions I would explore in a detailed implementation walkthrough.
05 / SUPPORTING EVIDENCEReview the role.
Review the role.
Discuss the systems.
Supporting paperwork is available for discussion. A focused review can connect my role to each system’s scope, the implementation and the project work managed in Asana.
- Role and association records
- Internal systems, editing engine and mailing-system scope
- My contribution and the decisions behind each system
- Asana project-management experience