Leanpub Header

Skip to main content

Filters

Category: "Management"

Management

New to Leadership and Engineering Management? Read the Leadership and Engineering Management article

  1. Lean Publishing
    Lean Publishing
    Peter Armstrong

    This book explains the philosophy behind Leanpub, from its origin in "a book is a startup" to the present form. Lean Publishing is the act of publishing an in-progress book using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do.

  2. The Restaurant Profit Playbook
    The Restaurant Profit Playbook
    A Practical Guide to Menu Pricing, Food Cost Control, Inventory, Labor, and Profit Improvement for Independent Restaurants
    Hisham Mohamed

    Stop guessing where your restaurant's money goes. Learn how to control food and labor costs, price your menu intelligently, reduce waste, and build a practical plan to improve profitability.

  3. Next Stage Orgs
    Next Stage Orgs
    How Modern Organisations Grow, Evolve and Thrive
    Javier Camarasa Garcia

    How do modern organisations stay effective as complexity, technology, and uncertainty keep increasing? Next Stage Orgs explores how to design organisations around value, flow, adaptive governance, and continuous evolution, without relying on a single framework or fixed operating model.

  4. نظرية الألعاب -افهم كيف يدار العالم
    نظرية الألعاب -افهم كيف يدار العالم
    ﻛﻴﻒ ﺗُﻘﺮأ أﺣﺪاث اﻟﻌﺎﻟﻢ ﺑﻠﻐﺔ اﻻﺳﱰاﺗﻴﺠﻴﺔ: ﻣﻦ ﻏﺰة إﱃ ﺗﺎﻳﻮان، وﻣﻦ اﻟﺮﺳﻮم اﻟﺠﻤﺮﻛﻴﺔ إﱃ ﻣﻀﻴﻖ ﻫﺮﻣﺰ — ﺑﴩح وافٍ ، وأﻣﺜﻠﺔ ﻣﺤﻠﻮﻟﺔ، وﺗﻤﺎرﻳﻦ ﺗﻄﺒﻴﻘﻴﺔ
    Ahmed Almaghz
    No Description Available
  5. Choosing Strategic Priorities
    Choosing Strategic Priorities
    How to Focus Strategy When Resources Are Limited
    Nabal Kishore Pande

    How should an organisation choose its most important priorities when resources cannot support every ambition? This book presents a practical framework for comparing options, making trade-offs, allocating resources and turning strategic choices into focused execution. It includes worksheets and decision tools to help leaders make priorities clear, defensible and actionable.

  6. Walden for the Cinema Age

    They occur in theaters, hallways, reception areas, and festival programs. They accumulate into economic outcomes without being measured directly.The result is an industry that frequently makes decisions with less information than it could possess.

  7. Executable Knowledge Architecture (EKA) - VOLUME 4b -- Semantic Knowledge Engineering, Part 2
    Executable Knowledge Architecture (EKA) - VOLUME 4b -- Semantic Knowledge Engineering, Part 2
    The Semantic Knowledge Development Lifecycle (SKDL) -- Chapters 23-27
    Xiaoqi Zhao

    You know how to build classes in Protégé. But do you know when to attach meaning — and when to wait?Volume 4 of "Mastering Ontology Engineering" introduces SKDL: the Semantic Knowledge Development Lifecycle. Seven stages. One discipline. Zero guesswork.From Aristotle to Description Logic. From taxonomy to executable knowledge.This is where pizza -> philosophy — and philosophy -> engineering.

  8. DIAGNOSE FIRST
    DIAGNOSE FIRST
    Finding the Real Problem Before Choosing the Solution
    Nabal Kishore Pande

    Before you spend time and money fixing a problem, make sure you understand what is causing it.A practical method for finding the real problem before choosing the solution. Learn to examine evidence, test competing explanations, identify the cause worth addressing, and check whether your response works.

  9. DECIDE WELL
    DECIDE WELL
    Making Better Decisions When Information Is Incomplete
    Nabal Kishore Pande

    A practical eight-stage method for making better decisions when information is incomplete. Learn to separate facts from assumptions, compare realistic options, test key uncertainties, record your reasoning and review the result.

  10. The Decision That Changed Nothing
    The Decision That Changed Nothing
    How to Separate Assumptions from Evidence and Make Better Decisions
    Nabal Kishore Pande

    A detailed plan does not always lead to a better decision. Learn how to separate facts from assumptions, identify the unknowns that matter, and test your beliefs before taking action. This short, practical book includes a decision-review worksheet you can use in your own life or work.

  11. Operation Research: Concepts, Techniques and Applications

    Master Operations Research Through Concepts, Techniques, and Practical Problem-SolvingLearn Linear Programming, Simplex Methods, Transportation, Assignment, TSP, Network Analysis, CPM, PERT, Queuing Theory, Game Theory, and Sequencing through structured explanations, numerical examples, and step-by-step problem-solving techniques.

  12. Adaptive Organisations
    Adaptive Organisations
    Thriving in Complexity
    Society for Adaptive Organisations

    The organisations that win are not the biggest or the fastest. They are the ones that learn faster than their environment changes.

  13. 把实践变成知识
    把实践变成知识
    从现场经验到可复核、可更正、可维护的公共成果
    永飞扬

    把“我做成过”变成别人能够追问、复核、迁移、更正和长期维护的实践成果。

  14. Agile Constraints Management
    Agile Constraints Management
    Agile, Constraints Management and Throughput Economics for Collaborative Knowledge-Work and Software Engineering Management
    Steve Tendon

    Bridge the critical gap between Agile delivery and bottom-line business performance. Agile Constraints Management introduces a revolutionary framework that merges Agile adaptability with the Theory of Constraints and Throughput Economics. Stop chasing team-level "velocity" and start driving measurable economic throughput by pinpointing hidden bottlenecks, forecasting with scientific precision, and managing work through outcome-focused MOVEs.

  15. Trustworthy AI
    Trustworthy AI
    Risk Governance under NIST AI RMF and ISO/IEC 42001
    Andrii Bogdanovych

    Fragment 1 — Chapter 1, "Introduction": why AI governance is a governance question, not an engineering oneWhen an organization first faces a decision to deploy an AI system — whether a credit-scoring model, an automated resume-screening tool, or a customer-support chatbot — the most common governance mistake is to treat that decision like an ordinary IT project: define the requirements, select a vendor, implement, and hand the system over to operations. Artificial intelligence technologies do rely on software and computing infrastructure, and in that sense they resemble any other IT initiative. But they differ in how they generate risk, and that difference calls for a distinct governance approach rather than a simple extension of familiar project management.Risk-oriented AI governance starts from a different premise: before discussing rollout timelines, budgets, or functional requirements, an organization has to answer the question "what adverse consequences could this system cause, for whom, with what likelihood, and how severe would they be" — and, alongside it, "how much of that harm are we willing to tolerate for the expected benefit." Fragment 2 — Chapter 3, "Trustworthy AI: Seven Characteristics of Trust": why explainability and interpretability are not synonymsConsider an AI system that automatically sorts incoming support tickets by priority. Explainability answers the "how" question: which features of the incoming text (keywords, tone, customer history) contributed to the computed priority score and with what weight — a technical account of the computation mechanism. Interpretability answers the "why" question for this particular ticket in the context of the system's business purpose — that is, whether a high priority score means "this customer is losing money right now" or "this customer is statistically likely to cancel," and whether that meaning matches how a support agent should act on it. The two characteristics support each other but serve different governance needs: explainability matters more to the engineer debugging the model, interpretability matters more to the agent or manager who must act on the system's output without understanding its internal mechanics. Fragment 3 — Chapter 18, "The Running Case": where ISO and NIST illuminate each other's blind spotsPrecisely because NIST explicitly requires, in its own standalone subcategory, a designated authority to deactivate a system, and no direct equivalent exists in Annex A of ISO, an organization that implements only ISO/IEC 42001 without checking it in parallel against the AI RMF risks missing this requirement altogether — it dissolves between the adjacent, but not identical, controls A.6.2.5 (release criteria) and A.3.2 (roles and responsibilities). This is a compelling, concrete example of the argument the book already made back in Chapter 1: the two frameworks do not compete but mutually illuminate each other's blind spots. Fragment 4 — Chapter 18, the book's closing paragraphAI risk management, as this book has shown it, never concludes with a signed document. It concludes — and immediately begins again — with the next MAP cycle, the next internal audit, the next policy review, the next model version, which has to be brought into operation just as thoroughly documented, traceable, and responsibly managed as the one before it.