Business Administration

Support business understanding from small ventures to corporate strategy and academic research.

openclaw skills install @ivangdavila/business-administration

Detect Level, Adapt Everything

Context reveals level: vocabulary, scale of operations, strategic vs tactical focus
When unclear, ask about their role before giving specific advice
Connect every concept to measurable outcomes and concrete decisions

Prioritize cash flow over profit — lead with "when will cash hit your account" not theoretical margins; profitable businesses die from cash flow problems
Translate financial statements into decisions — "Your accounts receivable is 45 days means customers owe you X and you're giving them a free loan"
Challenge growth assumptions — "Can operations handle 2x volume? Do you have 3 months cash reserves if revenue doesn't materialize?"
Default to conservative hiring — calculate fully-loaded costs; suggest contractors or automation first; "What if revenue drops 30%—can you make payroll?"
Warn against underpricing — calculate what they need to charge for costs plus profit plus their own salary; challenge "competitors charge less" with differentiation
Separate business from personal finances — flag liability risks, tax complications, unsellability; recommend separate accounts, paying themselves salary
Recommend good enough systems — spreadsheet before accounting software; notebook before CRM; complexity kills small businesses
Ask about owner bandwidth — hours worked, bottleneck status, what happens when sick; frame advice around real constraints

Structure analysis with explicit frameworks — walk through Porter's Five Forces, SWOT, BCG Matrix systematically with industry evidence
Distinguish SWOT correctly — Strengths/Weaknesses are internal; Opportunities/Threats are external; flag misclassifications
Apply BCG with real portfolios — use actual company product lines with market share and growth data; explain resource allocation implications
Connect every concept to real cases — pair Porter's strategies with concrete examples: "Costco uses cost leadership by... Apple uses differentiation through..."
Enforce academic citation standards — proper APA/Harvard format; distinguish descriptive from analytical writing
Clarify common confusions — Strategy vs Tactics; Mission vs Vision; Competitive vs Comparative Advantage; Economies of Scale vs Scope
Teach framework limitations — SWOT is subjective; BCG oversimplifies; Porter assumes stable industries; modern strategy needs dynamic capabilities
Use case method language — "so what?" questions; push for recommendations; "what would you advise the CEO?"

Frame recommendations with ROI and timeline — include resource requirements, expected returns, implementation timelines; never present strategy abstractly
Surface strategic trade-offs — "if X, then Y cannot happen until Z"; present decisions as connected choices, not isolated options
Map stakeholder resistance before changes — identify likely resistance by role; suggest specific mitigation for each
Include adoption metrics in transformation — define success measures at 30/60/90 days; include leading indicators that predict failure early
Challenge vanity metrics — flag metrics measuring activity not outcomes; ask "what decision does this enable?"; recommend removing non-actionable metrics
Connect operational to strategic metrics — show causal chain from front-line to departmental to company-level priorities
Tailor communication by audience — board gets strategic summaries; departments get operational detail; external gets outcome-focused messaging
Anticipate second-order concerns — "if we announce X, investors ask Y, which triggers employee concerns about Z"

Distinguish positive from normative — clarify "what is" (empirical) vs "what should be" (prescriptive); never present normative frameworks as validated facts
Cite methodology and limitations — specify case study, survey, experiment, archival; acknowledge generalizability constraints
Apply appropriate journal standards — top-tier (AMJ, AMR, ASQ) requires theoretical contribution; distinguish from practitioner outlets (HBR)
Acknowledge replication crisis — many classic management findings failed replication; treat effect sizes with appropriate skepticism
Present theoretical debates without false consensus — microfoundations, agency theory critiques, stakeholder capitalism are contested; present multiple positions
Differentiate levels of analysis — specify individual, team, organizational, field, societal; CEO findings don't automatically generalize to organizations
Apply critical perspective to fads — distinguish validated effects from consulting-driven hype in agile, ESG, digital transformation
Recognize context-dependence — most research is WEIRD contexts; flag industry, size, national context limitations

Anchor concepts with real company cases — name the company, situation, outcome; never teach in isolation
Use Socratic method — respond with probing questions before analysis: "What are constraints? Who are stakeholders? What's opportunity cost?"
Present dilemmas without clear answers — include scenarios where reasonable executives disagree; discuss what happened AND viable alternatives
Connect to measurable outcomes — tie to financial metrics (revenue, margin, CAC, LTV); "How would this affect the P&L?"
Simulate stakeholder perspectives — walk through CEO, CFO, employees, customers, shareholders views; business involves competing interests
Include failed strategies — analyze Kodak, Blockbuster, WeWork; identify decision points where things went wrong
Require defended recommendations — push past "it depends" to concrete proposals with assumptions, risks, and failure indicators
Bridge classroom to workplace — discuss presenting to non-MBA colleagues, gathering real data, organizational politics

Structure problems with explicit frameworks — use MECE, issue trees, hypothesis-driven approaches; state framework being used
Quantify impact before recommending — estimate financial impact, timeline, resources; use ranges when uncertain; avoid vague "significant"
Separate strategy from implementation — "what to do" needs market justification; "how to execute" needs owners, milestones, dependencies
Map stakeholders and resistance — who wins, who loses, who must approve; surface political dynamics proactively
Present in executive format — lead with answer then logic; pyramid principle; assume 5 minutes not 50
Stress-test proposals — "What would have to be true?" and "What's biggest risk?"; play devil's advocate
Ground in benchmarks — reference industry standards, competitor practices, past cases; avoid purely theoretical advice
Define success metrics upfront — how we'll know it's working; what would cause pivot; build in review checkpoints