O. Nguyen Product & Design Lead

Mission report // M-06 · Climate tech

Verity Nature - Digital MRV

An end-to-end digital MRV platform for high integrity carbon credit cycle.

Role
Senior Product Manager (Execution & Rollouts)
Timeline
24 Months
Status
Shipped & Validated
Begin report

1. The TL;DR (Executive Summary)

The Purpose

To replace slow, paper-driven global carbon-auditing methods with a unified, high-integrity digital ecosystem capable of orchestrating remote workflows, tracking active assets, and validating technical data streams in real time.

The Problem

The market faced a deep operational hurdle: field data collection was highly fragmented, entirely offline, and decoupled from global institutional servers. There was no automated infrastructure to validate edge data or securely push features without risking cross-network synchronization errors.

The Solution

We engineered and launched a multi-platform ecosystem consisting of an offline-first mobile/tablet field app, a central administration portal, and asynchronous API sync pipelines. This established an end-to-end verifiable framework backed by strict software security and quality checks.

The Impact

Acted as the central engine for engineering and design alignment, delivering 100% adoption across targeted cross-market pilots while establishing:

  • Robust Client-Server Architecture (Offline-to-Cloud API Gateways)
  • Strict Pre-Launch Testing Evidence & Cyber-Security Protocols
  • Multi-Stakeholder Reporting Matrix (Engineers, Executives, and Global Partners)

2. Strategy, Agile Cadence & Discovery

Insight & Requirements Gathering

Partnered directly with the Chief Scientific Officer to decompose highly complex environmental and geospatial auditing parameters into concrete, data-dense technical Product Requirement Documents (PRDs). By translating abstract business logic into structural backlog line items, we removed engineering blockages and structured clear use cases for development sprints.

Stakeholders & Team Leadership

After establishing the core application architecture, I stepped up to lead the cross-functional delivery roadmap as Senior PM. I managed the design-to-development-to-rollout pipeline in a fast-paced environment, serving as the main liaison between engineering, legal compliance teams, and executive management to coordinate dependencies.

Constraints & Release Cadence

The project operated under intense release schedules requiring reliable software updates shipped to rugged, remote regions. This demanded a zero-tolerance policy for production bugs, forcing our sprint planning to center entirely around deterministic test case pipelines and strict version control.

3. Technical Execution & Rollouts (The “How”)

System Mapping

Start // 01

Field app

Technicians conduct field sampling and examinations.

02 // Community scouting

Mobile observation app

Community-led observations and scouting by non-technical staff.

03 // Portable data center

Verity Edgecase

VSC — Verity Sync Case

Data backup and offline / online sync. Acts as a portable data center during field trips.

05 // Central data hub

Cloud data center

All data syncs back here when devices are online.

04 // Administration

Admin dashboard

Field-trip setup, data-field management, report generation, and analysis.

Local backup

Online sync

Review & analysis

Set up the next field trip

A continuous fieldwork loop, not a one-way pipeline: field and community observations are backed up through VSC, data syncs to the cloud when devices are online, and dashboard review and setup inform the next field trip. The loop runs horizontally on desktop and vertically on mobile.

Core Product Decisions

  • Deconstructed Feature Map: Broke down unstructured, massive scientific parameters into manageable API contracts and micro-workflows, allowing the platform to support evolving client requirements natively.
  • Client-Server Resilience: Spearheaded the development of an "Offline-First" client-server mobile architecture, ensuring full structural functionality without a network, coupled with automated edge-queue synchronization mechanisms.
  • Edge Token Automation: Engineered a metadata-driven validation engine utilizing automated GPS and camera hardware verification protocols to validate data authenticity before syncing with the central database.
  • Rigorous Rollout Governance: Established the platform's release criteria, enforcing a mandatory protocol where no build progressed to production without clearing exhaustive regression testing, automated code scans, and complete vulnerability patches.

Quality Assurance & Stakeholder Demos

  • Test & Demo Runways: Orchestrated comprehensive sprint validation cycles. I personally structured pre-release "runways"—ensuring all technical test cases were systematically completed and verified through explicit testing evidence reports.
  • Vulnerability & Security Scans: Integrated security scanning and loophole detection checks into the release pipeline, verifying code integrity to guarantee zero critical security leaks or data intercept risk prior to live executive stakeholder demos.

Visual Highlights

Publications