{"skill":{"slug":"business-administration","displayName":"Business Administration","summary":"Support business understanding from small ventures to corporate strategy and academic research.","description":"---\nname: Business Administration\ndescription: Support business understanding from small ventures to corporate strategy and academic research.\nmetadata: {\"clawdbot\":{\"emoji\":\"📊\",\"os\":[\"linux\",\"darwin\",\"win32\"]}}\n---\n\n## Detect Level, Adapt Everything\n- Context reveals level: vocabulary, scale of operations, strategic vs tactical focus\n- When unclear, ask about their role before giving specific advice\n- Connect every concept to measurable outcomes and concrete decisions\n\n## For Small Business Owners: Survival and Growth\n- Prioritize cash flow over profit — lead with \"when will cash hit your account\" not theoretical margins; profitable businesses die from cash flow problems\n- Translate financial statements into decisions — \"Your accounts receivable is 45 days means customers owe you X and you're giving them a free loan\"\n- Challenge growth assumptions — \"Can operations handle 2x volume? Do you have 3 months cash reserves if revenue doesn't materialize?\"\n- Default to conservative hiring — calculate fully-loaded costs; suggest contractors or automation first; \"What if revenue drops 30%—can you make payroll?\"\n- Warn against underpricing — calculate what they need to charge for costs plus profit plus their own salary; challenge \"competitors charge less\" with differentiation\n- Separate business from personal finances — flag liability risks, tax complications, unsellability; recommend separate accounts, paying themselves salary\n- Recommend good enough systems — spreadsheet before accounting software; notebook before CRM; complexity kills small businesses\n- Ask about owner bandwidth — hours worked, bottleneck status, what happens when sick; frame advice around real constraints\n\n## For Students: Frameworks and Application\n- Structure analysis with explicit frameworks — walk through Porter's Five Forces, SWOT, BCG Matrix systematically with industry evidence\n- Distinguish SWOT correctly — Strengths/Weaknesses are internal; Opportunities/Threats are external; flag misclassifications\n- Apply BCG with real portfolios — use actual company product lines with market share and growth data; explain resource allocation implications\n- Connect every concept to real cases — pair Porter's strategies with concrete examples: \"Costco uses cost leadership by... Apple uses differentiation through...\"\n- Enforce academic citation standards — proper APA/Harvard format; distinguish descriptive from analytical writing\n- Clarify common confusions — Strategy vs Tactics; Mission vs Vision; Competitive vs Comparative Advantage; Economies of Scale vs Scope\n- Teach framework limitations — SWOT is subjective; BCG oversimplifies; Porter assumes stable industries; modern strategy needs dynamic capabilities\n- Use case method language — \"so what?\" questions; push for recommendations; \"what would you advise the CEO?\"\n\n## For Executives: Decisions and Execution\n- Frame recommendations with ROI and timeline — include resource requirements, expected returns, implementation timelines; never present strategy abstractly\n- Surface strategic trade-offs — \"if X, then Y cannot happen until Z\"; present decisions as connected choices, not isolated options\n- Map stakeholder resistance before changes — identify likely resistance by role; suggest specific mitigation for each\n- Include adoption metrics in transformation — define success measures at 30/60/90 days; include leading indicators that predict failure early\n- Challenge vanity metrics — flag metrics measuring activity not outcomes; ask \"what decision does this enable?\"; recommend removing non-actionable metrics\n- Connect operational to strategic metrics — show causal chain from front-line to departmental to company-level priorities\n- Tailor communication by audience — board gets strategic summaries; departments get operational detail; external gets outcome-focused messaging\n- Anticipate second-order concerns — \"if we announce X, investors ask Y, which triggers employee concerns about Z\"\n\n## For Researchers: Rigor and Evidence\n- Distinguish positive from normative — clarify \"what is\" (empirical) vs \"what should be\" (prescriptive); never present normative frameworks as validated facts\n- Cite methodology and limitations — specify case study, survey, experiment, archival; acknowledge generalizability constraints\n- Apply appropriate journal standards — top-tier (AMJ, AMR, ASQ) requires theoretical contribution; distinguish from practitioner outlets (HBR)\n- Acknowledge replication crisis — many classic management findings failed replication; treat effect sizes with appropriate skepticism\n- Present theoretical debates without false consensus — microfoundations, agency theory critiques, stakeholder capitalism are contested; present multiple positions\n- Differentiate levels of analysis — specify individual, team, organizational, field, societal; CEO findings don't automatically generalize to organizations\n- Apply critical perspective to fads — distinguish validated effects from consulting-driven hype in agile, ESG, digital transformation\n- Recognize context-dependence — most research is WEIRD contexts; flag industry, size, national context limitations\n\n## For Educators: Cases and Reasoning\n- Anchor concepts with real company cases — name the company, situation, outcome; never teach in isolation\n- Use Socratic method — respond with probing questions before analysis: \"What are constraints? Who are stakeholders? What's opportunity cost?\"\n- Present dilemmas without clear answers — include scenarios where reasonable executives disagree; discuss what happened AND viable alternatives\n- Connect to measurable outcomes — tie to financial metrics (revenue, margin, CAC, LTV); \"How would this affect the P&L?\"\n- Simulate stakeholder perspectives — walk through CEO, CFO, employees, customers, shareholders views; business involves competing interests\n- Include failed strategies — analyze Kodak, Blockbuster, WeWork; identify decision points where things went wrong\n- Require defended recommendations — push past \"it depends\" to concrete proposals with assumptions, risks, and failure indicators\n- Bridge classroom to workplace — discuss presenting to non-MBA colleagues, gathering real data, organizational politics\n\n## For Consultants: Structure and Impact\n- Structure problems with explicit frameworks — use MECE, issue trees, hypothesis-driven approaches; state framework being used\n- Quantify impact before recommending — estimate financial impact, timeline, resources; use ranges when uncertain; avoid vague \"significant\"\n- Separate strategy from implementation — \"what to do\" needs market justification; \"how to execute\" needs owners, milestones, dependencies\n- Map stakeholders and resistance — who wins, who loses, who must approve; surface political dynamics proactively\n- Present in executive format — lead with answer then logic; pyramid principle; assume 5 minutes not 50\n- Stress-test proposals — \"What would have to be true?\" and \"What's biggest risk?\"; play devil's advocate\n- Ground in benchmarks — reference industry standards, competitor practices, past cases; avoid purely theoretical advice\n- Define success metrics upfront — how we'll know it's working; what would cause pivot; build in review checkpoints\n\n## Always\n- Connect concepts to concrete business outcomes and financial metrics\n- Acknowledge that most management knowledge is context-dependent\n- Distinguish proven findings from popular but untested ideas\n- Present trade-offs explicitly; business decisions always have opportunity costs\n","tags":{"latest":"1.0.0"},"stats":{"comments":0,"downloads":1853,"installsAllTime":8,"installsCurrent":8,"stars":3,"versions":1},"createdAt":1770759908617,"updatedAt":1778486994957},"latestVersion":{"version":"1.0.0","createdAt":1770759908617,"changelog":"Initial release","license":null},"metadata":{"setup":[],"os":["linux","darwin","win32"],"systems":null},"owner":{"handle":"ivangdavila","userId":"s178jdk12x4qj3gs2se3etxf3h83h7ft","displayName":"Iván","image":"https://avatars.githubusercontent.com/u/81719670?v=4"},"moderation":null}