Role / Accountability

Director, Operations & Finance (Founding Team)
Owned operational infrastructure, financial systems, and execution reliability for a high-visibility innovation platform at scale.

Environment

Public-facing innovation and crowdfunding platform with sponsors, startups, media attention, and large-scale public participation.

Timeframe

March 2012 – September 2014

What I Owned vs. Influenced

Owned

• • End-to-end operational systems and execution

  • Financial operations, budgeting, and reconciliation

  • Crowdfunding payout governance ($350K annually)

  • Vendor coordination and multi-office operations

  • Audit readiness and financial accountability

Influenced

• • Strategic direction of platform growth

  • Sponsor relationships and external partnerships

  • City buy-in and expanded support in future years
  • Startup participation and confidence in the platform

1. The Challenge

The Surface Problem

One Spark was conceived as a large-scale innovation festival connecting startups, creators, investors, and the public—and needed to move from vision to execution on an aggressive timeline.

The Real Constraint

This was not an ideas problem. It was a scale-without-infrastructure problem.

From the outset:

• • Public visibility was high
    
  • Expectations were external and immediate
    
  • Stakeholder volume was massive
    
  • Timelines were fixed and non-negotiable
    

Without durable operating systems:

• • Execution would break under growth
    
  • Coordination would become chaotic
    
  • Credibility would erode after early momentum
    

The core constraint was building operational infrastructure capable of supporting rapid growth without failure.

2. The Approach

Designing an Operating Model for Public-Scale Execution

Rather than treating One Spark as a one-time event, my focus was on establishing a repeatable operating model capable of supporting year-over-year execution under public scrutiny.

The approach emphasized:

• • Operational clarity across teams, partners, and vendors
  • Financial systems that supported scale, accountability, and transparency
  • Delivery processes resilient to public deadlines and reputational risk
  • Governance structures aligning leadership, sponsors, and civic stakeholders

The objective was not simply to “make it work,” but to make execution reliable and sustainable.

I held direct responsibility for designing and enforcing the operating model and financial governance across teams, partners, and execution cycles.

3. What We Built (Operating Infrustructure)

Installed capabilities included:

• • Operational planning and execution frameworks
    
  • Financial modeling, budgeting, and reporting systems
    
  • Cross-functional coordination structures for internal teams, vendors, and partners
    
  • Stakeholder communication and alignment processes
    
  • Delivery rhythms supporting repeatable annual execution
    

Together, these systems transformed One Spark from an ambitious concept into an operable, scalable platform.

4. Execution at Scale

• • Supported execution of a large-scale, public-facing innovation platform over multiple years
    
  • Enabled coordination across:
    1. Thousands of participating startups and creators
    2. Sponsors, investors, and civic partners
    3. Internal teams and external vendors
  • Operated under fixed timelines, public visibility, and high reputational stakes
    

The installed systems allowed the organization to scale without operational collapse.

5. Results

• • One Spark became an internationally recognized innovation platform
    
  • Supported participation from thousands of startups and creators
    
  • Enabled sustained, multi-year execution rather than a one-off event
    
  • Established operational credibility with sponsors, partners, and the broader community
    

The most important outcome:
The organization could reliably deliver at scale.

6. Endorsements / Validation

Signals of Success

• • Continued growth in participation and visibility
    
  • Ongoing sponsor and stakeholder engagement
    
  • Increasing organizational confidence in executing complex initiatives
    

These signals reflect trust in the operating model, not just enthusiasm for the concept.

7. Why This Matters

This case demonstrates:

• • Operations leadership under extreme visibility and pressure
    
  • Building systems before scale breaks execution
    
  • Translating vision into durable delivery infrastructure
    
  • Managing complexity across many stakeholders without losing control
    

This experience is foundational for senior Client Success, Delivery, and Operations leadership roles.

8. Key Takeaway

At One Spark, the challenge wasn’t creativity—it was building the operational and financial systems required to deliver reliably at public scale. My role was to put infrastructure in place so growth didn’t break execution.

Supporting Materials

Select materials used to support internal engagement and adoption: