Organizational Patterns & Management Concepts

← Back to Domain-Specific Families

Abstractions that name recurring patterns in organizations and system design, including governance and compensation structures (broadbanding, viable system model, academic administration), organizational antipatterns (mushroom management, doorman fallacy, magic pushbutton), and software or domain-modeling methods (feature-driven development, role class model, enterprise data modeling).

29 abstractions in this family — domain-specific abstractions that sit near one another in structural-signature space (k-means over structural-signature embeddings). Each is shown with its short description.

• Academic Administration — The coordinated governance and operational work through which a college or university manages academic affairs, students, records, finance, research, facilities, technology, compliance, advancement, and institutional strategy.
• Ambient Authority — Authority available implicitly from a subject's execution environment or identity, allowing an operation on a named object without the request carrying an explicit unforgeable authorization for that object and action.
• Broadbanding — A compensation-design method that consolidates many narrow salary grades into a few wide pay bands, allowing broader pay and lateral skill progression while reducing formal grade distinctions.
• Collaboration Graph — A graph whose vertices are declared participants and whose edges represent a specified pairwise collaboration relation within a stated scope and time window.
• Commons-Based Peer Production — Decentralized production in which contributors self-select modular tasks, coordinate and integrate work through shared information, and govern inputs or outputs as a commons rather than chiefly by hierarchy or price.
• Decartelization — The policy-driven dismantling of cartelized or monopoly-concentrated economic control through prohibition of collusion, breakup or deconcentration, entry measures, and institutional reforms intended to restore competitive decision making.
• Domain analysis — A software-engineering process that compares related systems and their business context to model commonality, variation, and reusable assets for a product family or domain.
• Dominant Logic — A firm's prevailing managerial frame for interpreting businesses and allocating resources, shaped by prior success and open to revision.
• Doorman Fallacy — The organizational error of automating a role's most visible task as if it were the whole role, while omitting latent service, coordination, security, signaling, and exception-handling value.
• Enterprise Data Modelling — The organizational practice of creating and governing a shared conceptual model of enterprise data—its business entities, meanings, relationships, rules, and authoritative vocabulary—across systems and projects.
• Feature-Driven Development — An iterative software-development method that builds an overall domain model and feature list, then plans, designs, inspects, builds, and integrates small client-valued features in short cycles.
• Magic Pushbutton — A UI and architecture antipattern that funnels a complex form and many unrelated business rules through one terminal button, causing monolithic logic and delayed feedback.
• Movie Packaging — An agency-led project-assembly arrangement in which represented writers, directors, actors, or other elements are combined before studio sale, historically in exchange for a packaging fee rather than ordinary commissions alone.
• Multi-source agreement — A voluntary multi-manufacturer specification that defines interfaces so independently produced components interoperate across vendors as a de facto standard.
• Mushroom Management — An organizational control pattern that assigns work while systematically withholding the strategic context, rationale, and feedback employees need to understand or adapt it.
• Organigraph — A graphic map of an organization's work relationships and flows rather than only its reporting hierarchy.
• Platform-specific model — A system-design model whose structure is expressed for a chosen programming, database, operating-system, or other implementation platform.
• Role Class Model — An object-modeling pattern that represents a context-dependent role as a separate class linked to a core object, allowing one object to hold multiple concurrent roles with role-specific state and behavior.
• Semantic Architecture — Software-architecture description using explicit machine-interpretable semantics for elements, relations, and constraints.
• Social Label — A socially interpreted designation applied or adopted to classify a person or group, linking the bearer to context-dependent category expectations that can organize interaction and feed back into identity or treatment.
• Software framework — Reusable software structure that coordinates an application while developers supply defined extensions.
• Translative Case — A grammatical case whose marked noun phrase denotes a resulting, assumed, or time-limit state—prototypically ‘becoming X’—with language-specific extensions such as role, language of expression, or completion by a deadline.
• Type Error — A detected mismatch between a program term's assigned or inferred type and the type required by the operation or context in which the term is used.
• Unified process — A customizable iterative software-development framework organized around use cases, architecture, early risk reduction, and four lifecycle phases from inception through transition.
• Vanishing hand — An industry-evolution hypothesis in which early managerial integration yields to more specialized market coordination as standards, capabilities, and exchange institutions mature.
• Verifiable Computing — Delegated computation that returns an output plus evidence enabling a client to check the specified result substantially more cheaply than recomputing, under explicit soundness and trust assumptions.
• Viable System Model — Beer's recursive organizational model mapping operations, coordination, control, environmental intelligence, and policy in an adaptive system.
• Virtual Design and Construction — A project-management methodology that integrates digital models of the facility product, delivery process, and project organization with performance metrics to plan, coordinate, and control design, construction, and operation against explicit objectives.
• Virtual Economy — A governed system of production, scarcity, exchange, and consumption of digital resources within a persistent virtual environment.