Olenoa
Menu

Selected work · Founder project

Digitizing operations for a multi-unit nonprofit organization.

Aareen Bekaa Association needed an internal system that could reflect different roles, operational units and real workflows without forcing the organization into a generic template.

Aareen Bekaa Association · Lebanon

The challenge

The operation was more complex than a generic dashboard.

The product needed to respect organizational structure and real operational responsibility—not flatten every user, record and decision into one undifferentiated interface.

  • 01Different organizational units
  • 02Different user responsibilities
  • 03Authorization and access boundaries
  • 04Operational records
  • 05Duty and mission workflows
  • 06Fleet visibility
  • 07Administration
  • 08Desktop, tablet and mobile use

This public case study excludes member names, internal identifiers, medical data, mission details, credentials, private contact information and sensitive operational records.

Approach

Start with roles, responsibilities and workflow.

The product was shaped around who is allowed to see or change information and how operational states move from one person or team to another.

  1. 01

    Role-aware access

    Users see the work relevant to their role and permissions.

  2. 02

    Modular operations

    Administration and operational areas remain structured without becoming isolated systems.

  3. 03

    Workflow reliability

    Operational transitions are explicit rather than informal.

  4. 04

    Responsive product design

    The system is designed for desktop and field-oriented tablet and mobile use.

Selected system areas

What was built.

A connected set of administration and operational workspaces, each shaped around its own responsibilities and safeguards.

01

Administration

Structured member and user records, organizational hierarchy, roles and permissions.

02

Ambulance & Emergency Operations

An operational workspace designed around emergency-unit workflows.

03

Duty workflows

Controlled duty records with workflow rules and operational safeguards.

04

Mission records

Structured mission workflows with reliability and idempotency logic behind critical actions.

05

Fleet

Vehicle lifecycle, history and operational fleet visibility.

Selected workflow design

A workflow is more than a status dropdown.

The value comes from connecting operational rules, responsibility and visibility—not simply digitizing a paper form.

  1. 01Readiness checkCapture the operational state
  2. 02Team Lead reviewPlace responsibility clearly
  3. 03Ready / Not ReadyMake the decision explicit
  4. 04Duty eligibilityConnect the outcome to the next workflow

Sanitized product preview

A real system, shown safely.

The public preview uses sanitized content and intentionally excludes production credentials, personal records and sensitive operational information.

Operational workspace
SANITIZED DEMO
READINESS WORKSPACE

Vehicle readiness

NOT READY
DEMO UNITUnit 211Readiness check in progress
3/4CHECKS
  • Oxygen kitAvailable
    READY
  • First aid kitAvailable
    READY
  • Portable suctionMissing
    BLOCKER
  • StretcherAvailable
    READY
Readiness check→Team Lead approval→Duty workflow
Authorized accessRole-aware modulesOperational overviewReadiness & workflow visibility

What the project proves

The interface is only one layer of the solution.

This founder project became part of the foundation for how Olenoa approaches operational technology today.

Explore Olenoa's operational system approach
  • Operational discovery
  • Product and workflow design
  • Permissions thinking
  • System architecture
  • Responsive interface design
  • Reliability around important workflow actions

Olenoa

Start with the operation.

If roles, workflows and operational visibility are difficult to manage, that is enough context to begin a useful conversation.

Discuss a similar challenge