Edward Jr. Balestra writes about leadership and building scalable operating models for healthcare technology companies, including enterprise readiness, product strategy, and decision-making.
They are most useful for healthcare technology leaders diagnosing growth, execution, or organizational bottlenecks.
Best for
A healthcare SaaS company needing a scalable operating model and repeatable enterprise implementation.
Not for
Sponsored LinkedIn posts promoting a vendor product to enterprise buyers.
Key takeaways
Healthcare software growth stalls from system design, not product quality.
An enterprise contract does not prove enterprise readiness; implementation and adoption matter.
Scaling requires clearer decision rights, not more meetings.
Check first: Ask for relevant examples and references, plus availability, day rate and scope boundaries.
Main ideas
Healthcare software growth stalls because of system design, not product quality · An enterprise contract demands a new operating standard; it does not prove the company has one · Not every request from a large customer should become the roadmap
Balestra writes about leadership and scalable operating models for healthcare technology companies.
They argue that growth depends on connecting product, sales, customer success, implementation, and executive decision-making—not optimizing each function in isolation.
Their posts offer practical ways to spot where that system breaks down, from enterprise delivery to unclear decision ownership.
Balestra turns scaling advice into concrete operating tests.
In Balestra's post on enterprise readiness, signing a large contract is only the start: readiness shows in disciplined implementation, user adoption, thoughtful product priorities, and measurable customer value.
In Balestra's discussion of executive leadership, they distinguish running a strong function from helping the business succeed across revenue, retention, implementation, and customer outcomes.
They also connect stalled growth to a fragmented operating model—where product becomes a feature factory and customer success reacts to requests—in Balestra's analysis of healthcare SaaS.
For teams struggling to make decisions, Balestra's post on decision rights offers a useful distinction: meetings can build context, but they cannot replace a clearly empowered owner.
These ideas make their work relevant to healthcare technology leaders diagnosing growth, execution, or organizational bottlenecks.
Balestra returns to one argument in different settings: healthcare technology companies usually stall not because of their product but because the operating model around it was never designed to scale.
The argument links several positions: executive leadership means owning business outcomes rather than running a function well; enterprise readiness comes after the contract, not at signature; large customer requests should not automatically become the roadmap; growth plateaus stem from system design; and scaling depends on named decision rights, not more meetings.
Each position is grounded in a specific stage of company growth.
Healthcare software growth stalls because of system design, not product quality
Balestra argues that healthcare software plateaus usually reflect organisational problems, not product ones.
Read more
Four patterns recur: product reports to the CTO and functions as backlog management rather than a business function responsible for positioning and turning the roadmap into revenue; the roadmap is rebuilt whenever a deal is at risk; customer success manages requests instead of expanding revenue at the executive level and feeding market insight back into the business; and product, customer success, and go-to-market operate independently, without connective tissue. The result is the same each time: every deal becomes custom, implementation slows, margins compress, and growth stalls.
The post names the misdiagnosis: companies think they have a product problem, but Balestra says they have a system problem. A numbered list lets readers check four patterns against their own companies.
An enterprise contract demands a new operating standard; it does not prove the company has one
Balestra argues that the habits that win early traction — flexibility, big promises, quick adaptation, customisation for early customers, and figuring things out alongside the client — do not scale to a large health system, payer, or national provider group.
Read more
Implementation cannot feel improvised, training cannot be invented live, and clients expect the vendor to know their workflows, define the rollout, identify super users, manage change, and drive adoption with discipline. Enterprise clients also expect measurable clinical, operational, or financial value, or a mix, visible quarter after quarter and carried consistently from sales promises through implementation, onboarding, customer success, support, and executive business reviews.
Balestra says the first million-dollar contract is a moment to evolve, not a sign the company has made it.
They turn that argument into questions a vendor should be able to answer: What did sales promise?
Where did the client expect value to appear?
Can you show, quarter after quarter, that the solution did what you said it would?
Not every request from a large customer should become the roadmap
This priority runs through two of Balestra's posts.
Read more
They write that every enterprise request cannot become the roadmap for the next two years.
Product leaders must distinguish requests that create the most value from one-off preferences and market signals, and identify the few that should shape broader product strategy.
Large strategic customers deserve attention and may need dedicated capacity, but that is a governance question, not a reason to let deal pressure set direction.
A roadmap that changes whenever a deal is at risk, Balestra argues, is a sales support function, not a product strategy.
Balestra says building whatever one customer asks for works from zero to one and kills you from one to ten. If the roadmap changes whenever a deal is at risk, the company has no product strategy.
Scaling requires decision rights, not more meetings
When a high-profile client wants to renegotiate or two functions clash over development priorities, the default is often to schedule one meeting after another until a month passes without a decision or an owner.
Read more
Balestra draws a distinction: debate needs a forum, the right people should pressure-test options, and meetings are not inherently wrong.
The failure is using them to substitute for decision rights.
Seeking full leadership-team alignment on every meaningful decision kills speed.
Scaling companies need to document who owns each decision, who provides input, who needs to be informed, and when debate ends.
Balestra offers concrete ownership examples: the product leader should decide product issues, while customer success, sales, or another commercial owner suited to the company's structure should decide client contract issues. Meetings can build context, but they cannot replace ownership.
Executives own business outcomes, not just a well-run function
Balestra distinguishes two kinds of accountability.
Read more
At director level, most of the role remains internal: whether the team executes, is structured correctly, and is improving process, quality, and consistency.
At VP level, the job becomes external and commercial: what the market is saying, which outcomes customers care about, where value is created or lost, and how the function connects to revenue, retention, margin, adoption, implementation, and customer value realisation.
A function can look healthy while the business is not.
The question shifts from whether your team is performing to whether the business is — and what you are doing to connect the pieces.
In healthcare technology, Balestra makes this concrete: Can sales and customer success communicate value with the right messaging and positioning?
Can implementation deploy the solution repeatedly without heroics?
Can customers adopt the workflow and measure the outcome?
They describe this as a pattern observed while mentoring and managing people, and note that the best directors usually broaden their view before they hold the title.
Start here for the clearest account of what Edward Jr.
Read more
Balestra diagnoses and how they frame a fix. It answers the question newcomers are most likely to ask: Why do healthcare software companies stop growing after early success, and what would a working operating model look like?
Balestra lists four recurring patterns behind stalled growth in healthcare software.
Product sits under the CTO and becomes a delivery function, building what sales or customer success requests instead of owning market positioning and turning the roadmap into revenue.
The roadmap becomes a feature factory where every at-risk deal can change priorities.
They say this works from zero to one customer but breaks from one to ten.
Customer success becomes reactive, managing requests instead of driving executive-level outcomes and feeding margin and market insight back into the business.
Product, customer success, and go-to-market also run separately, with no connective tissue to translate strategy into execution or revenue.
The outcome chain is consistent: every deal becomes custom, implementation slows, margins compress, and growth stalls.
Most companies, they conclude, think they have a product problem when they have a system problem.
For brands planning a campaign
For a fractional COO or VP of Operations brief, this post reads as a diagnostic checklist: whether product reports into the business or engineering, whether the roadmap survives deal pressure, whether customer success drives growth or manages a request queue, and whether functions share a planning rhythm. These are the first areas an operating-model engagement would audit.
This is the clearest example of Balestra reasoning from a specific company stage rather than a general principle.
Read more
It explains what changes operationally when a healthcare software company signs its first large contract, and why that moment can expose a business rather than confirm it.
Balestra argues that a first million-dollar contract is often the point when a company must evolve, not the point when it has made it.
Early traction usually comes from flexibility: promising a lot, adapting quickly, customising for early customers, and figuring things out alongside the client.
Those habits do not scale to a large health system, payer, or national provider group, where implementation cannot feel improvised and training cannot be worked out live.
Clients expect the vendor to understand their workflows, define the rollout, identify super users, manage change, and drive adoption with discipline.
Product must change, too: not every enterprise request should shape the roadmap for the next two years.
The work is to distinguish asks that create value from one-off preferences and market signals.
Enterprise clients also expect measurable clinical, operational, or financial value, or a mix.
Vendors must show quarter after quarter that the solution delivered what sales promised through implementation, onboarding, customer success, support, and executive business reviews.
Enterprise readiness, in this account, is proven after signature, not at it.
For brands planning a campaign
Useful for scoping an operating-model engagement around a specific transition: repeatable implementation, change management, roadmap-based request triage, and a value-realisation review cadence that reaches client executives. It also gives a concrete way to define "scalable" for a healthcare SaaS company.
This post answers what to do when a scaling company's leadership team cannot make decisions quickly.
Read more
After the operating-model and enterprise-readiness arguments, it provides the mechanism-level detail: what actually has to be written down.
Balestra describes a familiar escalation: a high-profile client wants to renegotiate, or two functions argue over development priorities, and senior leadership puts a meeting on the calendar.
They say that is not always wrong; the right people should discuss the issue and pressure-test options.
The failure comes next: meetings run long and over other meetings, people drop out, nobody owns the decision, and another meeting gets scheduled.
Schedules get messy, and a decision that was needed drags on for a month.
Their diagnosis: the meeting substituted for decision rights, and chasing full leadership-team alignment on every meaningful decision kills speed.
Scaling companies need more than functional roles; they need decision-making authority: who owns the decision, who provides input, who needs to be informed, and when debate ends.
For example, a product issue should sit with the product leader, and a client contract issue with customer success, sales, or whichever commercial owner fits the company's structure.
Meetings can create context; they cannot replace ownership.
For brands planning a campaign
This is the most reusable artefact for an operations engagement: a decision-rights map covering ownership, input, information, and when debate closes. It also offers a testable symptom for a diagnostics phase: whether recurring leadership meetings produce decisions or defer them.
This post explains the mindset shift Balestra's operating-model work implies for the people running it—important when a fractional engagement must be handed to an internal leadership team.
Read more
It answers what changes for a director moving into a VP-level role.
Balestra describes a career pattern they say they have seen repeatedly while mentoring and managing people in healthcare technology: the best individual contributor becomes a manager, the strong manager becomes a director, the director gets a function running well, and then looks toward a VP role.
The jump is not simply a bigger version of the same job.
At director level, much of the work remains internal: execution, team structure, consistency, process, quality, and accountability.
At VP level, the role becomes more external and commercially oriented, asking what the market is saying, what outcomes customers care about, and how the function connects to revenue, retention, margin, adoption, implementation, and customer value realisation.
In healthcare technology, that means asking whether sales and customer success have the right messaging, whether implementation can deploy repeatedly without heroics, and whether customers can adopt the workflow and measure the outcome.
The line they use to mark the change is that a strong functional leader makes their team better, while an executive leader has to make the system better—and a function can be green while the business is red.
For brands planning a campaign
Shows how Balestra frames an operating-model engagement: measured by business outcomes, not functional activity. Useful when deciding who inside the client organisation should own the work after handover and what to hold them accountable for.
Executive leadership as ownership of business outcomes
Balestra distinguishes between running a function well and being accountable for business performance.
Read more
They frame a Director's remit as internal execution — team structure, process, quality, consistency — while a VP is accountable for external and commercial results: what the market is asking for, where value is created or lost, and whether product, sales, customer success, and implementation connect to revenue, retention, margin, and adoption. A function can look healthy while the business is not; the key question is whether the whole system is working, not just your team.
Frames the argument as a career-progression pattern — strong individual contributor to manager to Director to VP — then shows where it breaks. Paired questions ('Is my team performing?' versus 'Is the business performing?') make the shift concrete.
For brands planning a campaign
Useful for a fractional operations brief when a client needs someone to work across functional silos rather than run one department. The material supports a pitch around cross-functional accountability and commercial outcomes, and lets a brand test whether Balestra thinks at the systems level a fractional COO role requires.
Enterprise readiness is earned after the contract, not at signature
Landing a large health system, payer, or national provider group is not the same as operating as an enterprise partner.
Read more
Balestra argues that habits that win early traction — flexibility, fast customization, promising a lot, figuring things out alongside the client — do not scale to enterprise delivery.
Implementation cannot feel improvised, training cannot be invented live, and the client expects the vendor to know its workflows, define rollout, name super users, manage change, and drive adoption.
Product discipline matters too: not every large customer request should become the roadmap.
The closing test is measurable clinical, operational, or financial value shown to the client over consecutive quarters and carried consistently from what sales promised through implementation, customer success, support, and executive reviews.
Contrasts mid-market and enterprise operating expectations, then turns them into questions a company should be able to answer about promised versus delivered value.
For brands planning a campaign
Directly applicable to a healthcare SaaS company that has landed enterprise logos but struggles to deliver repeatably. Supports a fractional operations engagement focused on implementation, onboarding, governance, and product-prioritization discipline rather than more selling.
Healthcare SaaS stalls on operating model, not product
Balestra diagnoses growth plateaus in healthcare software as a system-design problem.
Read more
They name four patterns: product reporting under the CTO and functioning as backlog management rather than a business function owning positioning and roadmap; a roadmap that changes whenever a deal is at risk, which they describe as sales support rather than product strategy; customer success managing requests instead of expanding revenue and feeding market insight back; and product, customer success, and go-to-market operating independently with no connective tissue. The common result is custom deals, slow implementations, compressed margins, and stalled growth.
A numbered four-part list pairs each symptom with the standard the function should meet, then reframes the assumed 'product problem' as a system problem.
For brands planning a campaign
Offers a framework for scoping an operating-model engagement, with specific problem areas to diagnose. A brand evaluating Balestra for a fractional COO role can use it as evidence that they start with organizational design, not tooling or headcount.
Decision rights, not more meetings, let a company scale
When a loud problem reaches senior leadership — a renegotiated contract, a fight over development priorities — the default response is to schedule a meeting, then more meetings, until a month passes with no owner.
Read more
Balestra argues that meetings are not the problem; using them as a substitute for decision rights is.
They make clear that debate needs a place, but pursuing total alignment on every meaningful decision kills speed.
Scaling teams need to define who owns the decision, who provides input, who is informed, and when debate ends, with product calls sitting with the product leader and contract calls with the commercial owner.
Uses an escalating meeting spiral as a recognizable scene, then replaces it with ownership questions that mirror a decision-rights model.
For brands planning a campaign
Useful when a client's stated problem is slow decision-making or meeting overload. Supports a fractional operations engagement focused on governance design — decision authority, escalation paths, and ownership — rather than process documentation alone.
The posts describe healthcare technology companies in general terms—enterprise customers, product organizations and go-to-market teams—but name no specific brand, employer, client, sponsor or partner business.
Read more
They read as firsthand observations from inside the industry, suggesting employment, but make no ownership or employment claim. Ask them to clarify any relevant company affiliation before booking.
Balestra writes about why healthcare technology companies stall as they scale, arguing that the cause is usually the operating model rather than the product.
The four posts form a connected argument.
The operating-model post names four patterns that block growth: product running as backlog management under the CTO, a roadmap rebuilt whenever a deal is at risk, customer success managing requests instead of expanding revenue, and product, customer success, and go-to-market working separately.
The enterprise-readiness post explains what changes after a large health system, payer, or national provider group signs.
The decision-rights post replaces the meeting spiral with named ownership.
The executive-leadership post draws the line between running a function well and being accountable for how the business performs.
Start with the operating-model post for the overall diagnosis, then read the other three for the specific failure points it implies.
Ask for video, podcast, transcript, or long-form samples; none was available.
Quintana also writes from a senior healthcare operating background, covering what executive-level leadership in healthcare organizations requires and where usual hiring judgments go wrong.
Read more
Both write for people making decisions about how a healthcare organization is run, rather than about a single tool or campaign.
Quintana's posts center on executive search and credentials, describing a career across Medicare, Medicaid, and Commercial environments. Balestra's work centers on operating-model design inside a software vendor, naming product, customer success, and implementation as the places growth breaks.
Hernandez writes about what happens to a SaaS customer after the sale, covering implementation handoffs, adoption, and the internal discipline that determines whether a customer keeps getting value.
Read more
Balestra's arguments about enterprise readiness and customer success cover the same ground.
Hernandez works at the level of individual handoffs and day-to-day practice, such as CRM adoption and details dropped between teams. Balestra works a level up, on the operating model and decision rights that should govern those handoffs.
Geil argues that a senior technology decision is a business decision.
Read more
They write for leadership teams working out how much executive capability they need and how to connect investment to an outcome. Balestra makes the same move for operations: the question is whether the business performs, not whether one function does.
Geil's subject is technology leadership and AI investment governance, including fractional and targeted CIO arrangements. Balestra's subject is healthcare software operations, specifically product strategy, customer success, and implementation under enterprise contracts.
Balestra’s posts speak to healthcare technology leaders dealing with scale: enterprise implementation, product priorities, customer outcomes, and operating decisions.
That makes them relevant to a healthcare SaaS company considering an operating-model engagement.
Before deciding on a paid placement, ask for recent LinkedIn audience analytics.
If a campaign depends on reaching specific job titles or seniority, request documented audience survey results or another source for those professional attributes; follower counts and post topics cannot verify them.
Balestra contains no documented sponsorship or partnership offer.
None of the four LinkedIn posts carries a brand partnership, sponsored-content label, or disclosed commercial collaboration, and the profile listing shows no media kit, rate card, audience deck, or partnership terms.
They write as a practitioner about operating models, enterprise readiness, and executive leadership in healthcare technology; the posts read as commentary rather than sponsored placements.
The only verified contact route is the LinkedIn profile, a general professional channel rather than a dedicated partnership inquiry line.
Buyers should ask directly about partnership terms before planning spend.
A healthcare SaaS company with roughly 40 to 120 employees signed two large health-system contracts in the past year.
Delivery is behind schedule, every deal is customised, and the board has asked the CEO to make implementation repeatable without adding headcount.
The company wants Edward Jr.
Balestra for a fractional COO or VP of Operations engagement, around two days a week for six months, to build a scalable operating model.
Reasons
The enterprise-readiness post addresses this exact transition. Balestra argues that habits which win mid-market traction—promising a lot, adapting quickly and customising around early customers—do not scale to a large health system or payer. Implementation cannot feel improvised: the client expects the vendor to know its workflows, define the rollout, name super users, manage change and drive adoption.
The operating-model post offers a ready diagnostic frame for the first weeks of the engagement: whether product sits under engineering as a delivery function; whether the roadmap moves whenever a deal is at risk; whether customer success is a growth lever or a request queue; and whether product, customer success and go-to-market share any connective tissue.
The decision-rights post supplies the mechanism. Balestra names the questions a scaling company has to answer: who owns the decision, who provides input, who is informed and when debate ends. They also give worked examples for product calls and contract calls, directly reusable in a governance workstream.
The executive-leadership post sets the standard for the client after handover: a function can be green while the business is red, so the engagement should be measured on business outcomes, not functional activity.
The posts support a services engagement: they show Balestra thinking through operating work, but document no sponsorship offer, media kit or partnership terms.
Gaps to confirm
The posts show how Balestra reasons, but not whether they have delivered this engagement before. They name no clients, completed operating roles, employers or references. Ask for relevant examples and references before signing a retainer, and confirm availability, day rate and scope boundaries.
When to choose a specialist
Poor fit as scoped.
Read more
Brief
A healthcare SaaS vendor wants to sponsor a run of LinkedIn posts in which Balestra promotes its new implementation-management product to enterprise buyers, with success measured by reach, comment engagement and demo requests.
Reasons
The posts document no sponsored-content label, media kit, rate card or partnership policy. Ask Balestra to confirm price, deliverables and disclosure practice before planning a campaign.
The posts provide no follower demographics, employers, occupations or seniority data, so the campaign cannot yet show that it will reach enterprise healthcare buyers. Request audience analytics before committing.
The posts are diagnostic commentary from a practitioner's point of view. They show no endorsement, comparison or promotion of a vendor's product—the core deliverable for this campaign. Ask whether Balestra is willing to create that kind of content.
All four reviewed pieces are written arguments; no video, podcast, audio or long-form article content is in scope. Ask whether Balestra can support those formats if the brief depends on variety.
If the buyer still wants a commercial relationship, confirm terms and audience data directly, then consider a co-authored or advisory format, such as a diagnostic session or written operating-model audit, rather than an awareness sponsorship priced on reach.
A worked campaign example
Campaign angle
Sell the engagement as a 90-day operating-model audit with named deliverables, not a broad advisory retainer. Pitch it this way: you signed enterprise contracts, but delivery still runs on the habits that won mid-market deals. We will define decision ownership, sort enterprise requests against the roadmap and establish a value-review cadence so the client sees the outcome every quarter.
First ninety days
A decision-rights map naming the owner, contributors, informed parties and the point at which debate closes, covering product, delivery and commercial decisions.
An enterprise-request triage rubric separating value-creating asks, one-off preferences and market signals, with a written rule for what enters the next roadmap cycle and what does not.
An implementation-readiness checklist covering operational processes, rollout plans, super users, change management and adoption owners for each live enterprise account.
A quarterly value-review template tracing what sales promised through implementation, onboarding, customer success, support and executive business reviews to a clinical, operational or financial outcome the client can see.
Open questions
Confirm whether Balestra takes fractional or interim engagements and on what terms. Ask about days per week, duration, rate and whether the work includes implementation-phase support or stops at operating-model design.
If the client also wants distribution or content support, request audience analytics and partnership terms; neither is published in the posts.
The posts do not verify employers or credentials. Request job-history details and client references rather than treating them as established facts.
Proof points
Point the client to the four published posts as the public basis for the approach: the operating-model diagnosis, enterprise-readiness argument, decision-rights model and business-outcome standard for executive leadership.
Use the decision-rights post as a sample governance deliverable: it states the ownership questions and applies them to product and contract decisions.
Choose Quintana when the constraint is healthcare operations rather than software delivery.
Read more
Her two posts target people hiring senior healthcare operators and describe 21 years in healthcare, beginning with patients in clinical settings and clinical research before moving into enterprise operations, payer strategy, provider network development and value-based care across Commercial, Medicare and Medicaid.
She cites scaling national programs, leading multi-state operations, growing provider networks, opening medical centers, and working within P&L and margin pressure.
If the client's six-month problem is payer relationships, network growth, or cost and MLR performance, her stated experience is closer to that challenge than Balestra's writing, which stays on the software side of the same industry.
Quintana argues that titles are easy to find and operational outcomes are not, positioning herself for boards and private-equity-backed healthcare organisations.
Her posts do not cover the software operating model: implementation repeatability, roadmap triage against enterprise requests, or the links between product, customer success and go-to-market.
Hiring her means buying operational and payer depth rather than a delivery-model fix.
If every enterprise deal is custom and implementation does not repeat, ask for examples of her work on that problem.
Her two posts establish her stated expertise, not how she has diagnosed or repaired a delivery model.
Choose Hernandez when the breakdown is downstream of strategy: adoption, handoffs and process trust.
Read more
Her posts describe that layer in detail.
One follows a sales conversation and implementation plan that go well, then a handoff that loses context: goals are not carried forward, risks go undocumented, support issues are disconnected from adoption, customer success lacks visibility into technical blockers, and the customer feels friction without being able to name it.
The other explains that a CRM can be configured correctly and still fail when users do not trust the surrounding workflow, leading them to work around it in spreadsheets and inboxes.
If the client's symptom is deals that implement but do not get adopted, or a process people quietly bypass, this is a tighter, easier-to-scope engagement than a broad operating-model mandate.
The remit is execution-level rather than executive.
Her posts address team-to-team operational discipline and customers' experience of internal handoffs, not decision rights, enterprise contract economics, or how product and commercial functions connect at the top.
Alongside a fractional operator, she complements the role; in place of one, governance and prioritisation questions remain open.
Before hiring, ask for client engagements, their length and scope, and experience beyond SaaS and CRM implementation contexts.
Choose Geil when the consequential decision is a technology one.
Read more
Her posts reframe the familiar question of whether a company is big enough to need a CIO as whether technology decisions have become consequential enough to require CIO-level judgment.
She sets out three working models: a full-time CIO, a fractional CIO alongside the executive team through growth or transformation, and a micro-fractional CIO brought in around one high-consequence decision.
The second post applies the same test to 2027 AI budgets, asking what outcome the money is meant to create, whether the data and processes support the use case, what new risk is introduced, who owns the initiative, and what funding it would displace.
If the client is about to commit budget to AI, replace or consolidate a platform, or set up technology governance and decision rights, she addresses that decision directly.
She is also the only one of the three whose posts state plainly that she sells fractional engagements and currently has some availability.
Her lens is technology and AI leadership rather than the commercial operating model.
She handles governance and decision rights at the technology layer; Balestra's argument covers product, delivery and contract calls, where a customised-deal problem usually sits.
Hiring her buys technology judgment, leaving implementation repeatability, enterprise request triage and the customer-success-as-growth-lever question to someone else—or to nobody.
Her posts describe what she would help decide at CIO level, not the delivery work below it.
If the client's gap is operational ownership under the executive team, ask who would own that work.
Her posts state her availability; ask directly about rates, engagement lengths, client names and outcomes.
This page draws on four complete written posts by Edward Jr.
Balestra, read in full rather than from titles or excerpts: arguments in the posts on executive leadership versus functional management, enterprise readiness after a large contract is signed, healthcare software operating models, and decision rights.
The posts have no publication dates, so they are organized by argument rather than in chronological order, and no change over time could be established from them.
All four are written LinkedIn posts in Balestra's own voice; the posts here include no video, podcast, transcript, book or long-form article.
Comparisons to other healthcare creators rest on two dated posts each from Jessica Quintana, Ianthe Hernandez and Erica Geil, so they reflect a sample of that work rather than a full reading.
Gaps left open: the posts name no employer, client, sponsor or partner, document no credential or engagement history, provide no audience composition data, and contain no sponsorship or partnership terms.