Holding the line on scope to ship an Exec Plugin's first-ever site in one week
Delivered the product's first website with a single designer in one week and driving up to a 45% increase in sales
Role
Duration
Tools
Team
Project Overview
The Exec Plugin Leadership Story shows me pushing back, repeatedly, against scope creep with a single designer and a one-week deadline — because protecting a timeline sometimes means saying no to the people asking for more.
5+
Feature heighlights
60%
Improved conversion
Agile
Delivery in a week
Problem Statement
Exec Plugin had never had a dedicated site — the plugin existed, but there was nothing to sell it with. When the stakeholder team requested a full microsite with a first draft due in two days, the bigger risk wasn't the timeline itself, it was scope. Requests kept coming in for more sections, more features, more "can we also add" — the kind of pressure that quietly turns a one-week project into a three-week one if nobody pushes back.
What I Led
Made the call to spend day one on understanding the stakeholder's actual goals — including whether to include pricing and an ROI simulation — before any design work started
Pushed back, repeatedly and firmly, on extra requests that would have blown the timeline, holding the team to a defined scope
Suggested the mascot as the site's visual anchor, to make the plugin memorable rather than another feature list
Sat with the content team to lock the site's storyline early, so scope stayed tied to a clear narrative instead of expanding indefinitely
What I Did Hands-On
Worked directly alongside the single designer on the project, giving direction section by section rather than only reviewing at the end
Ran a quick peer check with other designers when some interactive elements (the ROI calculator) weren't working, to find a fix fast without losing a day
Key Decisions & Trade-offs
Pushing back on stakeholder requests and said no to several late additions that weren't essential to the core pitch, risking stakeholder friction in the short term to protect the delivery date.
Spending day one on alignment, not design and cost visible progress on day one of a two-day sprint to first draft, but prevented building the wrong thing under pressure.
Mascot-led branding chose a distinctive character over a standard enterprise-software look, betting on memorability over convention.
Including pricing and the ROI calculator openly, showed value transparently instead of gating it behind a contact form.
Final Design
The Turning Point
Midway through, requests kept arriving for more than the site could realistically hold in the time we had. I raised my voice on it — plainly telling the stakeholder team what the site could and couldn't accommodate, and holding that boundary even as more asks came in. That pushback, not just the plan, is what kept the one-week delivery intact.
Impact
Delivered Exec's Plugin first-ever website, built and executed by a single designer under my direction
Shipped in one week despite ongoing pressure to expand scope
Drove up to a 45% increase in sales — the product had no site to sell against before this
What I Learned
Protecting scope under pressure isn't just a planning skill, it's a leadership one — it means being willing to say no to people above you when the timeline depends on it.
