Mohammad Walid
Strategy and product leader, building systems and ecosystems for AI and new technology. From an emerging market to global scale. ex-Founder · ex-Amazon.
Agent view: the full portfolio as plain text, for AI agents, recruiters' tools and search. Markdown version: llms-full.txt. Human site: home.
Summary
Built a startup, A.R.I.E.S., that created National Instruments' market in Pakistan (2012–2019) → Program Manager, Penn State Nittany AI Alliance (2020–2021) → Senior Operations Manager, Amazon, leading 30+ managers (2021–2025) → Senior Manager, CI · Direct-to-Consumer Domain Lead, ShipMonk, owning a ~$90–95M annual-revenue domain across 12 buildings (2025–2026).
Generalist operator across strategy, operations and product; founder background; B2B and enterprise customers; cross-functional leadership. At Amazon also owned product operations for vision pilots (returns and freight-type classification; camera confirmation at sorter diverters through a peak event).
Looking for: Leadership roles in strategy or product, in AI and AI-enabled technology.
Role families: Chief of Staff (CoS) / Founder's Office · Strategy & Operations (S&O) / Business Operations (BizOps) · GTM Strategy & Operations · Product Operations · Product Management (PM) · Technical Program Management (TPM) · AI Deployment / Deployment Strategy · Special Projects / Strategic Initiatives
Basics
Location: Riverside, CA (Pacific time). Email: mohammad_walid@hotmail.com. LinkedIn: https://www.linkedin.com/in/mohammad-walid. Education: MBA, Penn State Smeal College of Business (2021); B.S. Computer Science, COMSATS University Islamabad (2013). Experience: 2012–2026 across founder, program, operations and product leadership. Résumé PDF: /resume/Mohammad_Walid_Resume.pdf.
Building National Instruments' market in Pakistan: go-to-market and ecosystem
A.R.I.E.S. (technology startup) · 2012–2019 · Open the case · Lenses: Strategy, Leadership & Transformation
Building a market, then making the technology useful through funded laboratories, trained practitioners, research partnerships and industrial deployment.
- Context
- In 2012 I built a startup, A.R.I.E.S., to bring advanced test, measurement and control technology into Pakistan. National Instruments, a Texas-based test and measurement company, had one person covering Pakistan, serving a single existing account. Outside that niche the market was greenfield: academic, research, industrial and government projects across Pakistan, with clear gaps.
- What happened
- Pakistan had huge inertia for new technology. The demand was there, but three barriers held it back: access, getting the technology functional, and people who could use it. The go-to-market had to work on all three, not just sell hardware.
- What I led
- NI's go-to-market for Pakistan, end to end, through a local import partner, a local engineering partner and NI's own teams. 50+ proposals to funders such as ADB and USAID, and the lab designs.
- What lasted
- NI assigned its own lead to run the market. Four Centers of Excellence and a LabVIEW academy (250+ certifications) kept producing trained users, and at least four major clients kept coming back with harder problems.
Results
- Market: $3M+ a year NI revenue for three years running, against a $1M target; ~$7M pipeline, against a $3M expectation; ~$10M from Punjab, 2014 to 2018; 10 of 10 top target institutions by 2019; ~80% of the target market; Own lead NI assigned its own lead to run the market when I left
- Building it: 250+ institutions mapped and segmented; ~90% of academic and research funding traced, over five years; 50+ proposals to ADB, USAID and similar funders; First gate first major client won on a multi-year approved budget; $200K+ of unused NI hardware at one customer put to work
- Adoption: 4 Centers of Excellence with priority universities; 250+ LabVIEW certifications (CLAD) in under two years, academy opened November 2014; 4+ major clients coming back with harder problems; Showcased institutions presenting their NI labs and partnerships at their own conferences
- Delivery: 20–30 deployments across power and electrical, mechatronics, communications, sensing and automation; 12 people on the largest project: six developers, four on deployment, two on training; Research airship program with papers from 2014, a Massive MIMO testbed, ML in real-time control loops; Award assistive wheelchair with a student startup team, NI Asia award
- Public sector: 3 national testing labs designed for a government energy agency: battery, UPS and LED; 0.70 → 0.85 campus power factor from a low-cost audit method; 1 of 2 national transformer testing facilities, test automation through factory and site acceptance
Evidence for: GTM Strategy & Operations, Strategy & Operations (S&O) / Business Operations (BizOps), Chief of Staff (CoS) / Founder's Office, Special Projects / Strategic Initiatives
Keywords: Go-to-market, Market entry, Ecosystem building, Segmentation, Business development, Technology adoption, go-to-market strategy, market entry, emerging markets, 0 to 1, founder, startup, built a market from zero, business development, partner ecosystem, channel strategy, partnerships, funding strategy, market mapping, segmentation, ICP definition, pipeline building, proposal writing, donor and development funding (ADB, USAID), multi-year public budgets, public sector, higher education, research institutions, technology adoption, customer enablement, training and certification, supply chain, procurement, import logistics, contract management, product operations, technical solution design, stakeholder management, executive relationships, National Instruments, LabVIEW, test and measurement, instrumentation, $3M+ a year against a $1M target, new-market strategy, ICP segmentation, repeatable GTM launch, territory and account planning, B2B and public-sector accounts, account strategy, technical demos, customer discovery, customer validation, commercial expansion, first operator, founding hire, generalist
National testing labs: from a campus power audit to a provincial energy agency
A.R.I.E.S. (technology startup) · 2014–2018 · Open the case · Lenses: Strategy, Leadership & Transformation
A campus power audit, the same method in public buildings, then the certification regime and testing labs for a new energy agency.
- Context
- From 2014 to 2018, through my startup, I worked with a couple of educational institutes to build domain-specific Centers of Excellence. The country was suffering 12 to 16 hours of load shedding a day, and a new government energy-efficiency agency was in the works.
- What happened
- I partnered with the institutes to develop the technical delivery structure and solutions of the Centers of Excellence. One of these became the hub where I worked with the institute to develop a low-cost power auditing and smart load-balancing solution. The solution was then used to audit several government buildings and the burn unit of a hospital. After I met the head of an upcoming provincial agency, PEECA, these projects became the basis of a working relationship, and I partnered with PEECA on certification benchmarking and the testing laboratory designs.
- What I led
- The audit method and campus pilot with an early-stage partner and student developers, then the hospital and government audits. At PEECA: the certification benchmarking, the technical side of the regime, the lab designs with the NI team, and business development with the agency's incoming head, including the first conferences and technical proposals.
- What lasted
- Three national testing labs, designed on National Instruments technology, since built.
Results
- Campus pilot: 0.70 → 0.85 campus power factor, from 0.70–0.75; ~1/3 of the campus electricity bill had been power-factor penalties; 12–16 h of load shedding a day, the context for the pilot
- Public buildings: Hospital audit led to a power upgrade for the burn unit; Government building audits with the same method (details confidential)
- National testing labs: 3 national testing labs designed (UPS, LED and battery), powered by National Instruments, since built; Five-star certification regime adopted, based on the Southeast Asian model; ~6 months working with the agency's incoming office
Evidence for: Strategy & Operations (S&O) / Business Operations (BizOps), Special Projects / Strategic Initiatives, Technical Program Management (TPM), AI Deployment / Deployment Strategy
Keywords: Public-sector strategy, Policy and standards, Lab design, Energy efficiency, Stakeholder management, government partnerships, public agency, policy advice, certification regime benchmarking, standards, compliance, energy audit, power factor correction, load balancing, testing infrastructure, lab design, test methods, calibration, safety requirements, procurement specifications, business case, physical systems, hardware, national testing labs, UPS, LED and battery testing, cross-sector stakeholders, standards and certification, regulatory benchmarking, government relations
Transformer test automation at a national testing facility
A.R.I.E.S. (technology startup) · 2015–2017 · Open the case · Lenses: Product & Platforms, Applied AI & Decision Systems
Automating high-voltage transformer testing at one of the country's two national facilities, through factory and site acceptance.
- Context
- Transformer testing at one of the country's two national transformer testing facilities ran by hand, including discharging with a 10-foot pole. The university also held NI hardware it wasn't using.
- What happened
- I treated measurement, test sequence, discharge and safety as one system, built on hardware the university already owned. Automated sequencing, interlocks and automatic discharge replaced the manual steps, including discharging with a pole, and the bench went through factory and site acceptance and technology transfer.
- What I led
- Solution definition and partner coordination for transformer test automation at one of the country's two national transformer testing facilities: the measurement and control architecture, test sequencing, calibration checks, safety interlocks and controlled discharge, through factory and site acceptance and technology transfer. The facility and specialist teams handled the physical deployment.
- What lasted
- An accepted test-automation capability, handed over to the facility through technology transfer.
Results
- Facility: 1 of 2 national transformer testing facilities in the country; 2015–2017 requirements through factory and site acceptance; 3 of 5 of the institute's branches running NI technology
- System: HIL hardware-in-the-loop test bench; Safety interlocks, automatic discharge, lockout/tagout; FAT / SAT factory and site acceptance passed
Evidence for: Technical Program Management (TPM), AI Deployment / Deployment Strategy, Product Management (PM)
Keywords: Test automation, Hardware-in-the-loop, Safety systems, Acceptance testing (FAT/SAT), Systems integration, control systems, real-time systems, LabVIEW, NI RIO, instrumentation, data acquisition, industrial automation, high-voltage testing, interlocks, lockout/tagout, calibration, requirements definition, solution architecture, partner coordination, factory acceptance testing, site acceptance testing, technology transfer, deployment, mission-critical systems, hardware/software co-development, test engineering, rapid prototypes, manufacturing test
Nittany AI Alliance: building the AI delivery function
Penn State · Nittany AI Alliance · 2020–2021 · Open the case · Lenses: Product & Platforms
Turning an AI lab's informal client work into a delivery function: intake, planning, client reviews and handover across three programs.
- Context
- The Nittany AI Alliance at Penn State had talented developers and real clients, but no delivery function. Client knowledge lived with the director and a departing program manager, and projects ran on chat threads and a shared document.
- What happened
- I took over the full client-to-delivery lifecycle: intake and scoping, sprint planning across three programs, bi-monthly client reviews, and acceptance and handoff. I coached the developers to present their own work to clients, so the program no longer depended on one spokesperson, then helped hire a permanent program manager and handed it over.
- What I led
- The Alliance's delivery program as its only program manager under the director: 12 developers across three client programs.
- What lasted
- A repeatable delivery structure, developers presenting to clients on their own, and a permanent program manager I helped hire and handed the program to.
Results
- Delivery: 12 developers across three client programs; 2 programs delivered: the donor system and the aerospace test environment; In use donor system still running at Penn State
- Handover: Handed over to a permanent program manager I helped hire and onboard; Asked to stay the director asked me to stay on after my MBA
Evidence for: Technical Program Management (TPM), Chief of Staff (CoS) / Founder's Office, AI Deployment / Deployment Strategy
Keywords: Program management, Delivery operations, Client governance, Team building, Applied AI delivery, AI/ML solution delivery, intake, scoping, sprint planning, agile, client management, stakeholder updates, acceptance, handoff, hiring, coaching, building a function from scratch, university-industry partnership, 12 developers, three programs, PMO, portfolio delivery, program planning, resourcing and utilization, client delivery, delivery cadence, AI program management, university–industry delivery
Penn State donor system: ML outreach built on how relationships work
Penn State · Nittany AI Alliance · 2020–2021 · Open the case · Lenses: Product & Platforms, Applied AI & Decision Systems
Product and delivery for an alumni and donor engagement system that is still in use at Penn State.
- Context
- Penn State's alumni and donor teams didn't need a ranked list of likely donors. They needed outreach that respected how relationships work: who owns each relationship, how recently someone was contacted, and what kind of outreach fits.
- What happened
- Instead of shipping a donor score, I turned the outreach team's practice into rules the model couldn't override: relationship ownership, contact cadence and outreach type. I ran the intake, the reviews of model and rule behavior, testing and the user workflow, and brought my successor into the client history so the system kept running.
- What I led
- Product and delivery: communication intake, sentiment analysis, donor classification and the marketing MLOps workflow, integrated into the university's outreach work. Faculty owned the models.
- What lasted
- The alumni and donor system is still the solution in use at Penn State.
Results
- Outcome: In use still the solution at Penn State; 4 connected capabilities: intake, sentiment, classification, MLOps; Faculty owned the models; I owned product and delivery
Evidence for: Product Management (PM), AI Deployment / Deployment Strategy, Product Operations
Keywords: Applied ML, Product delivery, Decision rules, MLOps, Deployment and adoption, product management, ML product, sentiment analysis, classification, NLP, outreach, guardrails, requirements, user workflow, deployment, documentation, still in use, higher education, donor intelligence, stakeholder adoption, AI deployment, workflow discovery, solution design, configuration, launch and adoption, measurable impact, deployment strategy, customer workflow
ML testing environment for flight ops: recovering a grounded program
Penn State · Nittany AI Alliance · 2020–2021 · Open the case · Lenses: Product & Platforms, Applied AI & Decision Systems
When wildfires grounded an aerospace sponsor's LiDAR flights, the program moved to simulation instead of waiting.
- Context
- An aerospace sponsor's model-testing program depended on drone LiDAR flights. California's wildfires grounded them, and waiting meant losing the program.
- What happened
- When the wildfires grounded the drone LiDAR flights, I moved the program to simulation instead of waiting. We built two environments in Blender and Maya with virtual LiDAR in AirSim, and tested path planning and classification of six element types against them. I ran weekly sponsor reviews and was clear that field performance still needed real flights.
- What I led
- Recovery, scope and delivery for an aerospace sponsor's model-testing program, across simulation, scenes and LiDAR, and the models.
- What lasted
- A model-testing environment that no longer depended on flights, handed over with the program.
Results
- Outcome: 2 simulated environments, not datasets from the field; 6 element types for classification; ~6 months from a stalled program to a working test environment; Handed over with the program to the sponsor
Evidence for: Technical Program Management (TPM), AI Deployment / Deployment Strategy, Product Management (PM)
Keywords: Simulation, Program recovery, LiDAR and perception, Sponsor management, Model testing, digital twin, AirSim, Blender, Maya, virtual LiDAR, point cloud, path planning, object classification, computer vision, evaluation, validation boundaries, aerospace, dependency management, weekly governance, risk management, synthetic data, sensor data, data operations, test scenes, robotics and autonomy testing, dataset quality
Amazon hybrid sorter: a live retrofit through Prime Day
Amazon · 2022–2023 · Open the case · Lenses: Strategy, Leadership & Transformation
Leading an $11M hybrid-sorter retrofit in a building that kept shipping, through Prime Day and the network's decision on the design.
- Context
- An $11M hybrid-sorter retrofit at my Amazon site, one of four pilots. The building had to keep shipping through eight months of construction in four phases, with 30% to 60% of the floor unavailable. The end of the project coincided with Amazon's second-highest volume event, Prime Day.
- What happened
- The end of construction ran into Prime Day, and the plan assumed the building would go straight back to its normal peak target. I modeled the whole chain instead: demand, the planned execution for each construction phase, and actual execution on the floor. With planning, Finance and the project stakeholders I built three scenarios from those models. They showed what a shortfall here would do to the other buildings in the region, which were already near their limits: a modeled loss of about $12M a day. I took them to VP level and got approval to run to a realistic target and take extra freight where it helped the region.
- What I led
- I led the project at my site: the S&OP, freight and inventory management, and the execution plan through eight months of construction, then the Prime Day plan and the operating changes after launch. I owned the operating side, not the sorter's engineering design.
- What lasted
- The construction playbook went to other buildings, and I trained peers in two of them. Mine was the only one of the four pilot sites to deliver its high-volume event. The network decided against the hybrid design, and no other buildings got it.
Results
- Program: $11M hybrid-sorter retrofit, one of four pilot sites; 8 months of construction in four phases, 30–60% of the floor unavailable; 3/4 of construction carried by the pre-incline manual route
- Prime Day: ~$12M/day modeled loss under the original plan, avoided; 225K units delivered against a revised 220K commitment; 1 of 4 pilot sites to deliver its high-volume event
- After launch: +5% high-value throughput against the pre-project baseline; 5.1% lower operating cost; +3.2% regional throughput ($15M+ annualized); ~20% of the freight mix in a reciprocal exchange
- Transfer: 2 buildings where I trained peers on the playbook; Not scaled the network decided against the hybrid design beyond the four pilots; Promotion one of the main projects behind my move to Senior Manager
Evidence for: Strategy & Operations (S&O) / Business Operations (BizOps), Technical Program Management (TPM), Chief of Staff (CoS) / Founder's Office, Special Projects / Strategic Initiatives
Keywords: Executive escalation, Scenario modeling, S&OP, Program leadership, Risk management, Network planning, VP-level decision, capital project, $11M program, change management, construction phasing, capacity modeling, demand planning, sales and operations planning, inventory management, playbook, SOPs, peak readiness, Prime Day, risk quantification, ~$12M/day modeled exposure, Finance partnership, cross-functional, pilot evaluation, scaling decision, telemetry, automation retrofit, robotics and automation hardware, cost improvement, throughput, network operations, integrated operating plan, deployment capacity, special projects, hardware/software program, milestones and dependencies, decision follow-through, scenario planning, capacity planning, budget, PMO
Amazon ML planning platform: alpha testing before live operations
Amazon · 2023–2024 · Open the case · Lenses: Product & Platforms, Applied AI & Decision Systems
Alpha testing an ML extension of Amazon's planning platform, and turning its failures into requirements for the next version.
- Context
- Amazon's next planning platform brought ML-driven parameters into order prioritization and shift planning, so a building could control how much work it invited and how multi-order work was processed. It needed operational alpha testing at two sites before live use.
- What happened
- I built realistic parameter and workflow stress cases from how my site actually planned and ran shifts, and found two failures: scheduled headcount was being treated as usable capacity, and eligible work could be locked into manual batching before the shift could prioritize it. I held the high-volume test until the planner met its qualification criteria, even though the schedule wanted it sooner, and took both failures to the product team with fixes: precedence rules, adjustment bands with approval, and separating allocation from override permission.
- What I led
- Operational alpha testing at my site and the release recommendation. The central engineering and data-science team owned the planning engine; I owned testing and operating feedback.
- What lasted
- Two validated failure modes went back to the product team as requirements for its next version, and I led the first waves and wrote the playbook for retiring centralized planning in a second network.
Results
- Alpha: 1 of 2 alpha sites, and the only one to finish; 2 validated failure modes taken to the product team; Next version findings carried into the next development round
- Findings: 4–6 h labor-plan refresh that could overwrite operator decisions; Up to 10% adjustment bands proposed, with approval past the limit
Evidence for: Product Management (PM), AI Deployment / Deployment Strategy, Product Operations, Technical Program Management (TPM)
Keywords: ML product testing, Product requirements, Release gating, Decision-authority design, Launch criteria, alpha testing, user acceptance testing, product feedback, failure modes, human-in-the-loop, override design, guardrails, ML deployment, AI deployment, planning systems, order prioritization, capacity, labor planning, qualification criteria, launch readiness, partnership with engineering and data science, decision systems, operational risk, evals, evaluation criteria, deployment gates, cross-functional risk reviews, model launch readiness, operational readiness, rollout measures, safety and guardrails, alpha program
Manager readiness: an eight-week path adopted by up to eight sites
Amazon · 2021–2024 · Open the case · Lenses: Product & Platforms
Manager onboarding rebuilt around running the operation.
- Context
- Standard manager onboarding at Amazon was handovers and slide decks. It didn't teach the daily cadences, technical mechanics or cross-functional relationships a manager needed to run a shift alone.
- What happened
- I rebuilt onboarding for my own managers as an eight-week readiness path: four Wednesdays with every department, the full building flow whatever their home department, and a practical readiness check around day 60, judged on decisions observed on the floor rather than completed coursework. It started with nine managers and spread to up to eight sites.
- What I led
- Built the eight-week readiness path: cross-department rotations, visible decision checkpoints, safety audits and coaching loops.
- What lasted
- Up to eight sites adopted it as their primary manager onboarding.
Results
- Adoption: 9 managers in the first cohort at my building; Up to 8 sites using it as their primary manager onboarding; 8 weeks from start to readiness
Evidence for: Chief of Staff (CoS) / Founder's Office, Strategy & Operations (S&O) / Business Operations (BizOps)
Keywords: Leadership development, Enablement, Training design, Adoption across sites, onboarding program, manager development, curriculum design, certification, coaching, cross-functional rotations, safety audits, scaling a program, learning and development, people leadership, up to eight sites, operational readiness, technical enablement, training at scale, onboarding, multi-site rollout
The D2C operating platform: one source of truth for 12 buildings
ShipMonk · 2025–2026 · Open the case · Lenses: Product & Platforms, Applied AI & Decision Systems
Planning, live execution, quality and reporting for ShipMonk's D2C domain in one platform, built with Product and Data.
- Context
- Operators had no single source of truth. There was no internal tool for live dashboards, so they used Metabase and the ShipMonk app, HR ran on a separate platform, and nothing existed for shift planning or tracking. About half the metrics weren't reported, including subprocess cycle time.
- What happened
- I started with the shift planner and made it the standard in every building. Then, with Product and Data, I rebuilt the planning math, built subprocess cycle time up into bottom-up labor planning, and brought live execution, quality alerts and photo confirmation into one platform. Operations leaders used the same cycle times for continuous improvement. It replaced four to five separate sheets and calculators, and the operating model moved beyond its pilot.
- What I led
- With Product and Data: business logic, data lineage, definitions, requirements, operator workflows and adoption across 12 buildings, with the AI-assisted operations layer on top.
- What lasted
- The operating model moved beyond its pilot and was centralized, with one platform for operational tooling being adopted across the 12 buildings and the remaining domains as extensions. Every building moved from its own calculator to one shift planner.
Results
- Platform: 4–5 separate working tools and sheets replaced; 12 buildings on one shift planner; 32 data marts behind it; Centralized one platform for operational tooling, being adopted across the 12 buildings, with the remaining domains as extensions
- Outcomes: 70% faster operator decisions in the first AI-assisted operations deployment; More accurate headcount planning
Evidence for: Product Operations, Product Management (PM), Strategy & Operations (S&O) / Business Operations (BizOps), AI Deployment / Deployment Strategy
Keywords: Product ownership, Operating platform, Data modeling, Requirements and rollout, AI-assisted operations, Adoption at scale, product management, product operations, internal tools, platform, single source of truth, data lineage, business logic, requirements, roadmap, prioritization, Sigma, Snowflake, data marts, SQL, analytics, KPI design, metrics, workforce management, capacity planning, demand forecasting, shift planning, staffing, staffing manager, labor planning, real-time telemetry, quality alerts, retrieval-augmented generation (RAG), AI assistant, access control, change management, rollout, training, cross-functional with Product and Data, multi-site deployment, 12 buildings, direct-to-consumer, operator decisions 70% faster, workforce planning, launch readiness, customer and operator feedback into product decisions, issue triage, lightweight automation, internal AI tooling, workflow automation, AI-native operations, baselines and evaluation criteria, implementation, adoption and measurable value, enterprise rollout
ShipMonk D2C ownership: a $90–95M business, process and product
ShipMonk · 2025–2026 · Open the case · Lenses: Strategy, Leadership & Transformation
Owning the direct-to-consumer domain across 12 buildings in a role that had not existed: planning, the processes, the reviews, launches and merchant quality.
- Context
- ShipMonk's D2C business ran across 12 buildings at about $90–95M in annual revenue, and no role like mine existed. Shift planning didn't exist, labor planning wasn't built from demand in any structured way, only a sheet, and documentation didn't match newer workflows like photo confirmation and batching.
- My role
- D2C domain owner, with ownership spanning process, product, technical and C-suite reporting, as well as future solutions and designs.
- What I led
- The D2C domain end to end, including the full product: internal tooling, the order management side of the ShipMonk app, and every KPI and metric. Planning, launch readiness, SOP and RCA mechanisms, merchant escalations, and the WBR, MBR and QBR I designed, ran and presented to the CEO, CFO, CTO, CSCO and CPMO.
- What lasted
- One set of KPI definitions from the floor to the C-suite, documented processes that matched execution, managers trained to read the system, and a planning and reporting model that was centralized, with the remaining domains as extensions.
Results
- Merchants and quality: 60% → 85% Platinum and Gold merchant goal attainment; 92% → 96% packaging quality, against a 95% contract; $100K paid photo confirmation across two quarters, three merchants
- Packaging study: 197 before and after comparisons: 137 improved, 54 regressed, 6 unchanged; 6.41 s mean time saved per compared observation, about 314 hours in total; 117,938 orders in a carton-substitution study
- Scope and decisions: 12 buildings, about $90–95M in annual revenue; 3 planned facility designs changed through the Aisle Tax; Committee member of the technology transformation committee, driving AI adoption
Evidence for: Chief of Staff (CoS) / Founder's Office, Strategy & Operations (S&O) / Business Operations (BizOps), Special Projects / Strategic Initiatives
Keywords: Domain ownership, Executive reporting, Operating cadence, KPI design, Business reviews (WBR/MBR/QBR), business owner, $90–95M annual-revenue domain, general management, WBR, MBR and QBR, C-suite communication, operating rhythm, operating model, SOPs, root cause analysis, escalation management, launch readiness, customer experience, merchant escalations, cross-functional leadership, technology transformation committee, AI adoption, documentation, training program, process re-engineering, metric definitions, strategic planning, process design, planning cadence, goal-setting and OKRs, metrics cadence, executive decision support, cross-functional operating mechanisms, business operations (BizOps), strategy and operations (S&O), B2B customers (merchants), post-sales operations, customer escalations, headcount and capacity planning
The Aisle Tax
ShipMonk · 2025–2026 · Open the case · Lenses: Strategy, Leadership & Transformation
A building launch in my D2C domain turned into evidence that changed an approved facility design at three planned sites.
- Context
- Site 1 was a building launch in my D2C domain, and I was there to make sure the process could run and people were trained. A manager told me pickers were hitting constraints in the narrow aisles and work was getting slower. The narrow-aisle design had already been approved to add storage and was moving through the facility program.
- What happened
- Active construction was underway at the first of three planned buildings. I built the evidence from production telemetry, matched workloads across the two buildings so the work was comparable, and ran same-picker trials across shelf setups. I took it to my manager, the Chief Supply Chain Officer, who brought in the CEO. The next step was live model experiments, and their results became a design change for the three planned sites, including a retrofit of the one under active construction.
- What I led
- Data collection, data modeling, telemetry and process modeling, the picker experiments, executive reporting and the updated design, alongside my domain's launch readiness at Site 1. I had no capital-approval authority.
- What lasted
- Designs changed at three planned sites: Site 2 under active construction, and Sites 3 and 4 before construction began.
Results
- Decisions: 3 planned facility designs changed; Site 2 retrofit while under active construction; Sites 3 and 4 two sites changed before construction
- Telemetry (observational): 756,164 pick events, 685,115 valid; 25 s / 75 s typical pick, median and 90th percentile; 110 s / 257 s narrow-cart group of 2,734 picks, median and 90th percentile; +83 s weighted difference per pick across 835 matched products
Evidence for: Strategy & Operations (S&O) / Business Operations (BizOps), Chief of Staff (CoS) / Founder's Office, Special Projects / Strategic Initiatives
Keywords: Experiment design, Executive influence, Facility economics, Telemetry analysis, Business case, CEO decision, changing an approved decision, controlled trials, matched comparison, SQL, causal caveats, cost modeling, capital expenditure, design change, facility design, process modeling, data modeling, evidence-based decision making, launch readiness, executive reporting, 756K pick events, business case, ROI, cost-to-serve, quantitative analysis, decision memo, strategic analysis, labor economics
Photo confirmation: a paid merchant service at ShipMonk
ShipMonk · 2025–2026 · Open the case · Lenses: Product & Platforms, Applied AI & Decision Systems
Packaging and kitting escalations turned into photo confirmation on every pack station, switched on per SKU for merchants and internally for packaging issues, and launched as a paid merchant service.
- Context
- Packaging quality and kitting escalations kept coming from merchants, and there was no visual record of what left the building.
- What happened
- Photo confirmation came out of packaging and kitting escalations. I set it up on every pack station so any workflow could be switched on: per SKU for merchants, and internally for packaging and workflow issues. I offered it first to one heavy-kitting merchant and launched it as a paid service merchants could use as evidence.
- What I led
- Product and operations for photo confirmation as D2C owner: the service model (which SKUs and stations, what the camera captures, how merchants see each photo) and the paid launch.
- What lasted
- A paid service, $100K across two quarters with three merchants. The vision questions it raised continue in the AI Lab.
Results
- Service: $100K across two quarters; 3 merchants on the paid service; Paid value-added service
Evidence for: Product Management (PM), Product Operations, GTM Strategy & Operations
Keywords: Service launch, Visual evidence, Quality, Customer experience, Monetization, value-added service, paid service, customer evidence, escalation reduction, camera capture, product launch, pilot customer, kitting, quality assurance, human-in-the-loop, vision research follow-on in the AI Lab, $100K in two quarters, every pack station, per-SKU switch, commercialization, packaging and monetization of a service, customer pilot, B2B
Research partnerships
A.R.I.E.S. (technology startup) · 2012–2019 · Open the page
Through the startup, four Centers of Excellence and a LabVIEW academy (250+ certifications) behind the NI market, and the research platforms built on them: a flight-tested airship (papers 2014–2025), a Massive MIMO platform, an assistive wheelchair (NI Asia award) and a robotic bowling arm.
Keywords: Centers of Excellence, academic partnerships, research platforms, Massive MIMO, 5G research, airship, remote sensing, thermal imaging, assistive technology, multimodal input, robotics, mechatronics, FPGA, myRIO, LabVIEW academy, 250+ certifications