Portfoliov3.2 · 2026
BasedPhiladelphia, PA
FocusPlatform · Governance · Applied AI
StackJira · Power BI · SQL · Python

I build governance systems for teams — not project plans.

I turn messy enterprise workflows into governance products teams actually run on. Two case studies below — a 41-person governance OS and an AI supply-risk prototype — each shown with the decision log, tradeoffs, and the numbers.

Read case 01 monaniarya@gmail.com
§ 01How I think

Four beliefs that show up in every case.

  1. P.01
    Most teams don't need more coordination.
    They need better systems. Coordination load is a symptom; the product layer is the fix.
  2. P.02
    Status reporting should be a query.
    If leadership has to ask "what's the status?" the instrumentation isn't done yet.
  3. P.03
    Heroics are a product bug.
    A workflow that depends on specific people remembering things is an outage waiting to happen.
  4. P.04
    Adoption first, sophistication second.
    A mediocre system in daily use beats an elegant one that nobody opens.
§ 02Operating model

Discover → Define → Prioritize → Deliver → Optimize.

One spine for every case on this page. Each stage carries its own question, its own artifact, and its own signal of done.

  1. 01 / Discover
    What is the workflow actually doing today?
    Observation · user pain mapping · failure-mode interviews
    Signal: you can redraw the workflow without the team's help.
  2. 02 / Define
    Who's the user and what tradeoff matters?
    Problem statement · primary-user selection · success criteria
    Signal: a one-sentence problem the team stops arguing about.
  3. 03 / Prioritize
    What sequence maximizes adoption, not surface?
    Impact × effort · risk · strategic fit · sequencing
    Signal: the next three bets are obvious to anyone in the room.
  4. 04 / Deliver
    What is the smallest thing the user can run on?
    Requirements · workflows · dashboards · rollout · enablement
    Signal: the system survives a week without me in the channel.
  5. 05 / Optimize
    Where does the system still leak?
    Usage instrumentation · friction logs · iteration cadence
    Signal: the next release is sourced from data, not opinions.
§ 05Contact

Let's build the operating layer.

Product, platform, internal-tools, PMO-transformation, or applied-AI roles — especially where adoption, visibility, and measurable operating impact matter.

Accepting introductions through Q3 2026
Email
monaniarya@gmail.com
LinkedIn
linkedin.com/in/aryamonani
Résumé
Available on request