Real program discipline for Tampa's small businesses.
I'm Tyler Alexander, the founder. I started Cranes Consulting on a simple observation. The operating rigor that runs a $100M federal healthcare program doesn't need to cost $100M to implement. The frameworks are the same: risk registers, stage gates, KPI governance, standard work. The difference is how you scale them down without losing the discipline. I run every engagement personally, with a small bench of trusted partners I bring in for specialty work.
Founder
Tyler Alexander
Lean Six Sigma Black Belt · Founder & Lead Operations Partner
Based
Tampa, FL
Experience
10+ years
Sector depth
Federal healthcare, IT modernization, emergency response
Methodology
DMAIC, Agile, Prosci ADKAR
A decade running programs that can't fail.
Most of my career has been inside large federal healthcare organizations, running enterprise-scale programs where the failure mode wasn't a missed quarter. It was a national headline. That kind of environment forces a particular discipline: every initiative has a risk register, every deliverable has an audit trail, every system integration has a compliance sign-off.
On a federal Office of Emergency Management team, I led the design and rollout of an enterprise analytics program supporting nationwide emergency operations. That's the kind of program where governance, secure data infrastructure, and cross-functional alignment aren't "nice to have." They're the job. Earlier, on a national healthcare transformation team, I managed enterprise programs integrating multiple systems for ten national program offices, tracking 75+ KPIs across federal healthcare operations.
Here's what I kept noticing. Small businesses have the same operational failure modes as federal programs. Shelfware technology, missed handoffs, invisible margin leaks, runaway change orders, no single source of truth. The difference is they rarely have access to the discipline that prevents any of it. That's the gap Cranes Consulting exists to close.
Methodology
The core toolkit is Lean Six Sigma. Specifically, DMAIC for measurable improvement work and Prosci's ADKAR framework for the change-management side. Program governance is straight PMP-aligned: risk registers, stage-gate reviews, stakeholder mapping, clear RACIs. Data and reporting get built in Power BI, SQL, or whatever stack you already run.
None of this is proprietary. The frameworks are public. The value is in the judgement about which lever to pull, when, and how to scale it to a small-business context without dragging in the bureaucracy of the frameworks' original settings.
Why "Cranes"
Cranes are known for precision, patience, and an outsized lift capacity. Traits that describe both the work and the outcome we're aiming for. The logo is a flying crane with its neck extended forward, because the best operating improvements come from looking ahead instead of looking back.
Founder plus a small bench of partners.
Cranes is intentionally small. Tyler leads every engagement, and pulls in trusted partners with deep functional expertise when the work calls for it. You always know who is in the room, and the bill never includes anyone you haven't met.
Tyler Alexander
Founder · Lead Operations Partner
Lean Six Sigma Black Belt with 10+ years leading enterprise programs in federal healthcare and emergency response. Runs every Cranes engagement.
Partner network
Functional specialists, on call
A trusted bench of partners we bring in for specialty work: data engineering and Power BI, construction PM, HL7 FHIR and healthcare interoperability, federal grant compliance.
Certifications & training.
Lean Six Sigma Black Belt
Certified
Prosci Change Management
Certified Practitioner
Project Management Professional (PMP)
PMI
HL7 FHIR Fundamentals
Health Level 7 International
Healthcare Analytics Certificate
Nebraska Methodist College
B.S. Kinesiology
Southeastern Louisiana University
Principles that show up in every engagement.
Evidence, not opinions
Every recommendation is grounded in a measured baseline. If a claim can't be supported by data, it gets flagged as a hypothesis, not a finding.
Scope discipline
We only build what's asked. MVP first, iterate based on signal. No enterprise bloat, no speculative features.
Respect the team
The people running your operation daily know things we don't. The first week of any engagement is mostly listening.
Clean exits
Every engagement ends with a team that can run the new operating rhythm without us. That's the measure of success.
Let's see if we're a fit.
30 minutes. No deck. Bring a real problem.