Management DPF Suite
14 publications. Open a title to read, or expand its contents below.
Read the Suite introduction — Management DPF Suite
Community Management Principles Framework
Use this framework when people need useful participation, relationships or joint contributions: help one another, take part in a valued activity, keep shared work feasible, or make their experience useful elsewhere. A community organiser, participant, practitioner, sponsor or assisting agent can enter at the difficulty already present. When the proposed community is meant to support a wider cultural purpose, CB.1 also helps decide whether that purpose needs a community contribution at all.
Contents · 16 patterns in Community Management Principles Framework
- Table of Contents
Community Management Principles Framework Architectural Reference
- CB.Reference:1 - Useful participation and its wider contributions
- CB.Reference:2 - What makes the choice difficult
- CB.Reference:3 - Connect the methods through the contribution needed next
- CB.Reference:4 - Two ways to carry a practice, and why the distinction matters
- CB.Reference:5 - The work being performed, and the support it needs
- CB.Reference:6 - Recognise the problem, then establish the result
- CB.Reference:7 - What this publication preserves and where to return
- CB.Reference:8 - Actual supplier returns
- CB.Reference:9 - Renew the affected contribution
- CB.Reference:End
Applications
- CB.Application:1 - Application 1 - Obtain useful professional help and develop what recurs
- CB.Application:2 - Application 2 - Keep a voluntary garden workable through conflict and succession
- CB.Application:3 - Application 3 - Extend a practice without a discussion group
- CB.Application:4 - Application 4 - Separate customer help, learning and provider commitments
- CB.Application:5 - Connect an external development community with independent workplaces
- CB.Application:End
Corporate Finance Principles Framework
Methods for valuing investments, arranging finance, preserving liquidity, managing financial exposure and making corporate-finance decisions.
Contents · 22 patterns in Corporate Finance Principles Framework
- Table of Contents
Corporate Finance Principles Framework Architectural Reference
- FIN.Reference:1 - Problem frame
- FIN.Reference:2 - Problem
- FIN.Reference:3 - Forces
- FIN.Reference:4 - Solution
- FIN.Reference:5 - Archetypal Grounding
- FIN.Reference:6 - Bias-Annotation
- FIN.Reference:7 - Conformance Checklist
- FIN.Reference:8 - Common Anti-Patterns and How to Avoid Them
- FIN.Reference:9 - Consequences
- FIN.Reference:10 - Architectural Rationale
- FIN.Reference:11 - SoTA-Echoing
- FIN.Reference:12 - Relations
- FIN.Reference:End
Part E - Advice, renewal and continuing practice
- FIN.16 - Prepare a Finance Recommendation and Return It for a Decision
- FIN.17 - Refresh Financial Models and Data
- FIN.18 - Choose Whether and How to Change Corporate-Finance Methods
- FIN.19 - Reconcile Simultaneous Corporate-Finance Work Across Claims and Horizons
- FIN.20 - Deliberately Continue and Change Corporate-Finance Culture
Corporate Governance Principles Framework
A pattern language for making corporate decisions, arranging governing contributions, protecting rights and improving the ways these works are performed.
Contents · 17 patterns in Corporate Governance Principles Framework
- Table of Contents
Corporate Governance Principles Framework Architectural Reference
- CGOV.Reference:1 - Problem frame - Governing a corporation through particular acts
- CGOV.Reference:2 - Problem and forces - Joining competent contributions into an effective act
- CGOV.Reference:4 - Archetypal grounding - A bounded pilot commitment
- CGOV.Reference:5 - Bias, limitations and consequences
- CGOV.Reference:6 - Questions for use and recurrent failures
- CGOV.Reference:7 - Architectural Rationale
- CGOV.Reference:8 - SoTA-Echoing - Source contributions and their limits
- CGOV.Reference:9 - Relations, dependency and refresh
- CGOV.Reference:End
Part IV - Rights, consequences and renewal
- CGOV.12 - Protect Corporate Minority Holders’ Rights and Enable Contest or Exit
- CGOV.13 - Monitor Corporate Performance and Require an Account
- CGOV.14 - Decide Whether and How to Change Corporate Governing Instruments and Arrangements
- CGOV.15 - Decide Whether and How to Change Corporate-Governance Methods
- CGOV.16 - Reconcile Constituent and Encompassing Corporate Governance Work
- CGOV.17 - Deliberately Continue and Change Corporate-Governance Culture
Customization and Productization Management Principles Framework
Make customer-specific results and repeatable offerings supportable together.
Contents · 8 patterns in Customization and Productization Management Principles Framework
- Table of Contents
Customization and Productization Management Principles Framework Architectural Reference
- CUST.Reference:1 - Field and Use
- CUST.Reference:2 - Boundaries and the Meaning of the Name
- CUST.Reference:3 - Methods and Their Connections
- CUST.Reference:4 - Make the Whole Arrangement Work
- CUST.Reference:6 - Learn from Practice without Confusing the Result Levels
- CUST.Reference:7 - Recognition, Assurance and Correct Use
- CUST.Reference:8 - Consequences
- CUST.Reference:9 - Architectural Rationale
- CUST.Reference:11 - Supplying Methods and Reader Returns
- CUST.Reference:12 - Use and Refresh
- CUST.Reference:End
Customization and Productization Management Patterns
- CUST.1 - Manage Client Variation and Develop Repeatable Offerings
- CUST.2 - Recover Client Deltas and Choose Their Disposition
- CUST.3 - Develop a Repeatable Offering Family
- CUST.4 - Configure a Customer Solution and Place Differentiation
- CUST.5 - Run Field Learning and Return a Productization Candidate
- CUST.6 - Establish Repeatable Deployment and Service Delivery
- CUST.7 - Evaluate Growth and Customization with Full Resource Obligations
- CUST.8 - Change the Offering Family with Compatible Customer Transitions
Engineering Asset Management Principles Framework
A domain pattern language for making and revising value-oriented decisions about engineered assets over their lives, for one asset, an interacting asset System or a portfolio.
Contents · 16 patterns in Engineering Asset Management Principles Framework
- Table of Contents
Engineering Asset Management Principles Framework Architectural Reference
- EAM.Reference:1 - The working problem and practical gain
- EAM.Reference:2 - Forces and working distinctions
- EAM.Reference:3 - Architectural Rationale
- EAM.Reference:4 - Recognition, assurance and ordinary stops
- EAM.Reference:5 - Predictable mistakes, consequences and bias
- EAM.Reference:6 - Current sources and what they support
- EAM.Reference:7 - Qualified returns from related practice
- EAM.Reference:8 - Framework boundary and revision
- EAM.Reference:End
Part C - Alternatives, Conflicts, Combinations, and Timing
- EAM.7 - Generate Ways to Supply an Asset-Dependent Service
- EAM.8 - Generate Maintenance, Renewal, and Retirement Alternatives
- EAM.9 - Compare Asset Alternatives and Reconcile Decisions When They Conflict
- EAM.10 - Compare Engineered-Asset Portfolio Combinations
- EAM.11 - Time Asset Interventions and Manage Dependencies
Part D - Decisions, Outcomes, and Continuing Practice
- EAM.12 - Integrate Specialist Results for an Asset Recommendation or Decision
- EAM.13 - Track Realized Outcomes and Reconsider Asset Plans
- EAM.14 - Decide Whether and How to Change the Asset-Management System
- EAM.15 - Decide Whether and How to Change Engineering Asset-Management Methods
- EAM.16 - Deliberately Continue and Change Engineering Asset-Management Culture
Leadership Principles Framework
Helping participants act together, from a needed contribution to its useful performance and continuation.
Contents · 3 patterns in Leadership Principles Framework
- Table of Contents
Leadership Principles Framework Architectural Reference
- LDR.Reference:1 - The working situation and useful result
- LDR.Reference:2 - How the three leadership methods and their suppliers connect
- LDR.Reference:3 - What remains with other practices
- LDR.Reference:4 - Authority, cost and sufficient ordinary work
- LDR.Reference:5 - People, organizations and capable AI
- LDR.Reference:6 - How to use and question the result
- LDR.Reference:End
Connected use: a federation begins a joint evidence service
- LDR.Use:1 - A worthwhile proposal with incompatible contributions
- LDR.Use:2 - Advice changes the promise
- LDR.Use:3 - Agree a feasible first month
- LDR.Use:4 - Begin and complete a useful contribution
- LDR.Use:5 - Qualified autonomous AI changes the feasible whole
- LDR.Use:6 - Continuation after success is another substantive question
Management Accounting Principles Framework
Management Accounting helps a controller, accountant or manager explain how work uses resources and how that use appears in money, forecasts and performance accounts. Begin with the decision or account that needs a better explanation. A small model of the relevant work can be sufficient.
Contents · 9 patterns in Management Accounting Principles Framework
- Table of Contents
Management Accounting Principles Framework Architectural Reference
- MA.Reference:1 - The working problem
- MA.Reference:2 - How the methods connect
- MA.Reference:3 - A model that changes the next decision
- MA.Reference:4 - Correct use, evidence and effort
- MA.Reference:5 - Why this organization of methods
- MA.Reference:6 - Sources, qualifications and changed conditions
- MA.Reference:End
- MA.1 - Build the Resource-Consumption and Cost Model
- MA.2 - Explain the Cost and Use of Capacity
- MA.3 - Assign Shared Costs for the Stated Use
- MA.4 - Reconcile Operating, Reporting and Cash Accounts
- MA.5 - Construct and Update an Operating Forecast
- MA.6 - Separate Forecasts, Targets and Resource Requests
- MA.7 - Explain a Cost or Margin Difference
- MA.8 - Account for Customer and Product Economics Over Time
- MA.9 - Examine the Behavioral Effects of Management Accounting Information
Marketing Principles Framework
Understand a customer's situation, develop an offer that can be delivered, and change commercial work in light of the result.
Contents · 14 patterns in Marketing Principles Framework
- Table of Contents
Marketing Principles Framework Readme
Practical entries
- MKT-ENTRY-QUESTION - Find out enough to make the next decision
- MKT-ENTRY-CHOICE - Make one customer’s next choice workable
- MKT-ENTRY-MEDIA - Keep the promise intact when an intermediary changes it
- MKT-ENTRY-PROGRAMME - Share preparation while keeping promises feasible
- MKT-ENTRY-LEARNING - Offer learning while preserving the learner’s purpose
- How to use the language
Marketing Principles Framework Architectural Reference
- MKT.Reference:1 - Problem frame - Useful offers in actual customer situations
- MKT.Reference:2 - Problem and forces - Connect usefulness, choice and provision
- MKT.Reference:3 - Solution - Enter through the result that is missing
- MKT.Reference:4 - Composition and performance - Preserve the conditions of the whole
- MKT.Reference:5 - Recognition and assurance - Know what the evidence establishes
- MKT.Reference:6 - Bias-Annotation - Recover whose result and whose burden
- MKT.Reference:7 - Conformance and common failures - Follow the intended use
- MKT.Reference:8 - Consequences - What changes in practice?
- MKT.Reference:9 - Architectural Rationale - A repertoire with connected results
- MKT.Reference:10 - SoTA-Echoing - Preserve distinct answers to distinct questions
- MKT.Reference:11 - Relations - Obtain the contribution the receiving decision needs
- MKT.Reference:12 - Edition and use
- MKT.Reference:13 - Direct framework returns
- MKT.Reference:14 - Refresh the affected use
- MKT.Reference:End
Marketing pattern language
- MKT.1 - Qualify a Market Problem and Differences between Customers
- MKT.2 - Construct and Test an Offer and Its Positioning
- MKT.3 - Reach a Suitable Audience and Obtain a Meaningful Response
- MKT.4 - Make Choice and Acquisition Meaningful and Feasible
- MKT.5 - Develop and Align a Customer Experience Concept
- MKT.6 - Jointly Shape a Useful Result and Help Achieve It
- MKT.7 - Continue, Restore or End a Customer Relationship
- MKT.8 - Construct a Journey Map for a Specific Decision
- MKT.9 - Select an Offer or Help for a Particular Customer
- MKT.10 - Evaluate the Contribution and Cost of a Marketing Intervention
- MKT.11 - Align Promises, Partners and Execution
- MKT.12 - Investigate a Customer or Market Question for a Decision
- MKT.13 - Test Commercial Model Repeatability and Deployment Limits
- MKT.14 - Develop and Change a Programme for Selected Customer Organisations
Cross-pattern applications
MKT.Application:2 - APP-MKT-MEDIA - Keep a supportable offer through a changing intermediary
- MKT.Application:2.1 - Start from the offer and the work that can receive a response
- MKT.Application:2.2 - Obtain the intermediary’s actual contribution
- MKT.Application:2.3 - Construct the permitted family of meanings
- MKT.Application:2.4 - Connect observable events to the receiving decision
- MKT.Application:2.5 - Make exposure compatible with actual provision
- MKT.Application:2.6 - Compare filtering and mistaken blocking from the affected purposes
- MKT.Application:2.7 - Revise the failed connection and preserve the useful remainder
MKT.Application:4 - APP-MKT-ACCOUNT - Carry a customer’s changing question from first contact into useful work
- MKT.Application:4.1 - Prepare an encounter that can change the work
- MKT.Application:4.2 - Obtain access and let the case travel
- MKT.Application:4.3 - Turn grounds for action into a usable comparison
- MKT.Application:4.4 - Investigate a concern and prepare an attainable agreement
- MKT.Application:4.5 - Make implementation a receiving part of the agreement
- MKT.Application:4.6 - Choose continuation and reopen only the affected work
MKT.Application:5 - APP-MKT-LEARNING - Connect a learning offer with personal development and voluntary exchange
- MKT.Application:5.1 - Recover the different purposes before building one arrangement
- MKT.Application:5.2 - Obtain the learning product and the personal programme
- MKT.Application:5.3 - Keep community participation workable alongside the offer
- MKT.Application:5.4 - Let a condition of the whole change the constituent action
- MKT.Application:5.5 - Judge and maintain the distinct results
- MKT.Application:End
Operations Management Principles Framework
A domain pattern language for admission, continuation, coordination, service, quality, improvement and performance decisions in continuing operation.
Contents · 28 patterns in Operations Management Principles Framework
- Table of Contents
Operations Management Principles Framework Readme
Practical entries
- OPS-PUMPWORKS — Find the next supported controller-service decision
- OPS-SERVICE-WINDOW — Offer service that rooms, people and commitments can support together
- OPS-ACCEPTED-RESULT — Faster generation still leaves the promised result unavailable
- OPS-PRACTICE-CHANGE — Change the way of working without treating publication as successful use
- OPS-RELEASE-AND-WAIT - Change admission without losing the customer’s wait
- OPS-PROTECT-AND-DEVELOP - Prepare or learn while preserving promised service
- OPS-PREPARE-AND-RESPOND - Prepare useful work and keep a response possible
- OPS-ADVICE-IN-USE - Follow an operating explanation into the user’s work
- OPS-AIMS-AND-PERFORMANCE — Set a meaningful aim and interpret what follows
Operations Management Principles Framework Architectural Reference
- OPS.Reference:1 - Start from a difficulty in continuing operation
- OPS.Reference:2 - Competing demands on one operation
- OPS.Reference:3 - Work, descriptions, structures, and records remain distinct
- OPS.Reference:4 - Demand, commitments, subjects, and units remain distinct
- OPS.Reference:5 - Several management views can coexist on the same Work
- OPS.Reference:6 - Shared attention is stronger than visibility and weaker than consensus
- OPS.Reference:7 - The control branch is conditional
- OPS.Reference:8 - Pattern relations do not prescribe an operating lifecycle
- OPS.Reference:9 - Use the Methods together where their results meet
- OPS.Reference:10 - Conditions on a whole combination
- OPS.Reference:11 - Check the combined decision and its result
- OPS.Reference:12 - Architectural Rationale
- OPS.Reference:13 - Apply the repertoire in production and service settings
- OPS.Reference:14 - Gains, burden and limits of combined use
- OPS.Reference:15 - What this publication covers and leaves outside
- OPS.Reference:16 - Intended use and ordinary non-use
- OPS.Reference:17 - PatternID and reader order
- OPS.Reference:18 - Practical entry forms
- OPS.Reference:20 - FPF dependency and compatibility
- OPS.Reference:21 - Sibling-domain returns and availability
- OPS.Reference:22 - Available contributions
- OPS.Reference:23 - Representative case coverage
- OPS.Reference:24 - Edition return
- OPS.Reference:25 - Publication boundary
- OPS.Reference:End
Organization Administration Principles Framework
ADM helps administrators examine administrative requests, give justified refusals and provide usable results under the organization's rules. Its fifteen patterns also help improve the arrangements supporting this work by connecting organizational rules, participants, permissions, work and records. Establish any permission required for the action being taken; specialist decisions remain with the people authorized to make them.
Contents · 15 patterns in Organization Administration Principles Framework
- Table of Contents
Organization Administration Principles Framework Architectural Reference
- ADM.Reference:1 - The working problem
- ADM.Reference:2 - How the contributions connect
- ADM.Reference:3 - Different things, different accounts and different structures
- ADM.Reference:4 - Correct use and its cost
- ADM.Reference:5 - Why use this language
- ADM.Reference:6 - Sources, evidence and changed conditions
- ADM.Reference:7 - Applied framework instructions
- ADM.Reference:8 - Enabling provision and decision accounts
- ADM.Reference:9 - Using operational accounts
- ADM.Reference:End
Part B - Design the Repeated Case, Resolve Exceptions and Supply the Result
- ADM.5 - Design Reusable Instructions for Administrative Requests
- ADM.6 - Resolve an Administrative Exception
- ADM.7 - Check the Claim Needed for This Administrative Decision
- ADM.8 - Establish and Exercise the Required Permission for an Administrative Action
- ADM.9 - Provide a Usable Administrative Result
- ADM.10 - Reconcile Administrative Obligations, Performance and Records
Organization Change Engineering Principles Framework
A domain pattern language for changing an organization's contributions, working relations, and capability while its work continues.
Contents · 17 patterns in Organization Change Engineering Principles Framework
- Table of Contents
Organization Change Engineering Principles Framework Readme
Practical entries
- OCE-PUMPWORKS - Compare weekly AI-inspection work arrangements while service continues
- OCE-CONSEQUENCES - Keep a useful contribution while repairing the service it disrupts
- OCE-ASSOCIATION - Preserve contribution and authority across membership and service changes
- OCE-PRACTICE-CONTINUATION - Keep useful practice when names, examples and opportunities differ
- Citation
Organization Change Engineering Principles Framework Architectural Reference
- OCE.Reference:1 - From a bounded change to continuing organization development
- OCE.Reference:2 - Actual, formal, and possible claims remain distinct
- OCE.Reference:3 - Several structures and several views can coexist
- OCE.Reference:4 - Pattern relations do not prescribe a lifecycle
- OCE.Reference:5 - How the contributions connect
- OCE.Reference:6 - Conditions for using the contributions together
- OCE.Reference:7 - Architectural Rationale
- OCE.Reference:8 - Applying the language in different settings
- OCE.Reference:9 - Practical gains, costs and limits
- OCE.Reference:10 - Questions before relying on a combined result
- OCE.Reference:11 - Intended use and ordinary non-use
- OCE.Reference:12 - PatternID and reader order
- OCE.Reference:13 - Using the available Methods
- OCE.Reference:14 - Pattern selection and result relations
- OCE.Reference:16 - FPF dependency and compatibility
- OCE.Reference:17 - Method development and Implementation Facilitation contributions
- OCE.Reference:18 - Sibling-domain returns
- OCE.Reference:19 - Representative case coverage
- OCE.Reference:20 - Publication boundary
- OCE.Reference:End
Part II - Design Organization Relations and Work Arrangements
- OCE.4 - Design an Organization’s Contribution Architecture
- OCE.5 - Define Organization Positions
- OCE.6 - Establish Holder Assignments and Enabling Relations for Organization Change
- OCE.7 - Coordinate Product-or-Service and Organization Architecture Decisions
- OCE.8 - Compare Human, AI, Robotic, and Provider Arrangements for the Same Organizational Work Result
Part III - Realize Change While Work Continues
- OCE.9 - Realize a Bounded Organization-Capability Increment
- OCE.10 - Choose a Response to Participation or Working Culture Difficulties in the Target Organization
- OCE.11 - Coordinate Organization-Change Work with Continuing Service
- OCE.18 - Arrange Capability Development and Receiving Work in an Organizational Transition
Strategy Principles Framework
Each pattern starts with a recognizable working situation, the useful result and an ordinary non-use boundary. Its Solution explains the action; its case makes a consequential choice or stop visible. Conformance and evidence guidance help test the particular result without turning recognition into proof.
Contents · 17 patterns in Strategy Principles Framework
- Table of Contents
Strategy Principles Framework Architectural Reference
- STR.Reference:1 - Problem frame - Direction and commitment under changing conditions
- STR.Reference:2 - Problem - From attractive intentions to responsible choices
- STR.Reference:3 - Forces - What the comparison must hold together
- STR.Reference:4 - Solution - Connect the results the question needs
- STR.Reference:5 - Recognition and assurance - Understand the move, then support the claim
- STR.Reference:6 - Archetypal grounding - Three unlike applications
- STR.Reference:7 - Bias-Annotation - Whose contribution and whose burden?
- STR.Reference:8 - Conformance Checklist - Correct use of the connected language
- STR.Reference:9 - Common Anti-Patterns and How to Avoid Them
- STR.Reference:10 - Consequences - What changes in practice?
- STR.Reference:11 - Architectural Rationale - Why a connected repertoire?
- STR.Reference:12 - SoTA-Echoing - Current contributions, bounded transfers
- STR.Reference:13 - Relations - Obtain the professional results the decision needs
- STR.Reference:14 - Strategic-method synthesis
- STR.Reference:15 - Framework guidance and professional results
- STR.Reference:16 - Refresh the smallest affected use
- STR.Reference:End
Part IV - Revisit and Sustain Strategic Practice
- STR.12 - Observe Signals to Continue or Reconsider Strategic Direction and Commitments
- STR.13 - Choose and Maintain Strategy Methods
- STR.14 - Reconcile Simultaneous Strategic Work Across Horizons and Scales
- STR.15 - Deliberately Continue and Change Strategy Culture
- STR.16 - Construct a Feasible Portfolio with Shared or Branch-Specific Support
- STR.17 - Investigate Technological Change for Strategic Possibilities
Cross-pattern applications
STR.Application:1 - APP-STR-01 - Choose SensorCo’s response to commoditized AI inspection
- STR.Application:1.1 - The opening decision
- STR.Application:1.2 - Frame the uncertainty and preserve a serious rival
- STR.Application:1.3 - Use different futures because they change the comparison
- STR.Application:1.4 - Decide whether more inquiry is worth doing
- STR.Application:1.5 - Make the whole proposed arrangement visible
- STR.Application:1.6 - Select only the supported commitment
- STR.Application:1.7 - Reconsider in time and preserve independent work
- STR.Application:1.8 - Sustain useful methods and cultural practice separately
- STR.Application:2 - APP-STR-02 - A professional considering a new practice
- STR.Application:3 - APP-STR-03 - A public service under deep uncertainty
- STR.Application:End
References and other texts
- Management DPF Suite Architectural Reference
Management concerns choosing and sustaining the direction, commitments and provision of a collective undertaking, and changing them when the results or conditions warrant it. The undertaking may be a company, public service, professional practice, temporary collaboration or voluntary community. Its participants can have different purposes and decision rights. A shared employer is unnecessary; an actual basis for making and relying on a contribution is necessary.