Three recent roles — the scope, what I did, and what changed. The short version lives on my résumé.
The situation. The company's Asana workspace was a free-for-all — teams spun up disjointed new boards every month with no shared standards, tasks routinely fell through the cracks, and I found unassigned work dating back four years. Leadership had no cross-functional visibility into what was actually shipping.
What I did. I audited how all ten teams — from creative and sales to engineering and execs — actually used Asana, then architected a three-tiered workspace with standardized naming, custom fields, and automations to cut out manual data entry. I drove adoption by documenting the new system in our wiki and joining teams' daily standups, so they helped shape it rather than have it handed down.
The results. Pipeline confusion and cross-functional friction dropped sharply, and the four-year-old backlog was triaged and closed out in weeks instead of months. With clean, reliable data for the first time, teams could finally use the workspace to forecast capacity and plan resourcing proactively instead of just reacting.
The situation. Wide Eye's lead PM was leaving, and the agency needed someone who could ramp up fast and take over a blended team of designers and engineers running custom brand and web work across several high-profile projects, without missing a beat on delivery.
What I did. I owned day-to-day operations and resourcing in Harvest, Asana, Notion, and Airtable, running capacity planning, staffing, and workload balancing across projects while managing budgets and burn reports through the full lifecycle. I translated ambiguous stakeholder feedback into clear requirements, built reusable trackers and reporting templates adopted across the wider PM team, and automated status reporting in Slack that cut the time it took to pull a report in half.
I also built content production and management templates to make client handoffs smoother, and started experimenting with AI tools for meeting notes and surfacing patterns in client feedback. When I spotted room to expand a client's scope, I worked with sales and the client directly to help shape it.
The results. My teams shipped $2.6M+ of brand and web work without burning out. Capacity was planned, budgets stayed predictable, and burn was visible weeks ahead instead of after the fact. The Slack automation and reporting templates became the team's default way of working, and half of my clients during that time expanded their scope or moved to a retainer.
The situation. Our agency was using Basecamp for both internal engineering work and external client communication. This shared setup created a serious liability: raw, internal technical debates and messy bug triaging were at risk of becoming visible to our clients. At the same time, Basecamp's minimalist feature set was holding our developers back. They needed a dedicated tool to run modern, agile sprints, but our monolithic workflow was capping their velocity and putting client trust at risk.
What I did. To fix the workflow bottleneck and secure our data, I led a zero-downtime migration to separate our client and internal communication tracks:
The results. The migration completely eliminated the risk of clients seeing internal development notes. By tailoring the workflow to how our engineers actually work, we streamlined our QA ticket triage and made the handoff from design to development incredibly clean. Ultimately, this structural change compressed our handoff timelines by a full seven days and drastically improved our delivery precision.
"Mingwei was fantastic. I wish she could manage all my projects and my whole life. I couldn't have worked with a better team."