Proposal Workflow Pattern
Also known as: RFC Pattern, Decision Proposal Process
Pattern Name: Proposal Workflow Pattern
Use Case: When a user wants to create a proposal, get feedback, and then submit it for approval.
Description:
This pattern orchestrates a multi-step proposal process. It begins with the user drafting a proposal. Once the initial draft is ready, the system facilitates a feedback loop where stakeholders can review and provide comments. After incorporating feedback, the user can finalize the proposal and submit it for formal approval. The system then tracks the approval status and notifies the user of the outcome.
Workflow:
- Draft Proposal: The user creates the initial version of the proposal.
- Feedback Loop: The proposal is shared with designated reviewers for feedback.
- Incorporate Feedback: The user revises the proposal based on the feedback received.
- Final Submission: The user submits the finalized proposal for approval.
- Approval Tracking: The system monitors the approval process and provides status updates.
- Notification: The user is notified of the final approval or rejection.
Examples:
- A project manager drafting a project proposal and sharing it with team leads for feedback before submitting it to the steering committee.
- A sales team creating a sales proposal, getting it reviewed by legal and finance, and then sending it to the client.
- A student writing a thesis proposal, getting feedback from their advisor, and then submitting it to the university for approval.
1. Overview
[Content to be added]
2. Core Principles
[Content to be added]
3. Key Practices
Key practices for this pattern include careful design, iterative implementation, and continuous monitoring.
4. Implementation
Implementation requires understanding the system context and applying the pattern incrementally.
5. 7 Pillars Assessment
| Pillar | Score (1-5) | Rationale |
|---|---|---|
| Purpose | 3 | Serves a clear technical purpose in system design |
| Governance | 3 | Can be governed through standard engineering practices |
| Culture | 3 | Supports engineering culture of reliability and quality |
| Incentives | 3 | Aligns incentives toward system stability |
| Knowledge | 4 | Well-documented pattern with extensive community knowledge |
| Technology | 4 | Directly applicable to modern technology stacks |
| Resilience | 4 | Contributes to overall system resilience |
| Overall | 3.4 | A valuable technical pattern that supports commons infrastructure |
6. When to Use
This pattern is applicable in distributed systems and platform architectures where the described problem is encountered.
7. Anti-Patterns & Gotchas
Common mistakes include applying this pattern without understanding the specific context and constraints of the system.
8. References
See sources in frontmatter.