Technology architecture pack
Ratings for the Technology architecture pack
Set technology standards, reference architectures and platform roadmaps for infrastructure, cloud and networks
Who it is for. Technology, infrastructure, cloud and platform architects who describe the baseline and target technology architecture, set the standards and reference architectures, and plan the platform, cloud, network, resilience, security, cost and observability decisions the roadmap depends on.
244 blocks, 78 prompts, 6 prompt sets, 64 variables, in 19 topics. Version 2.
Made for Pro. Every download starts with 14 days of Pro, so you can add this pack today and use all of it; on the Free plan you can add it and read it, with your library read-only until you move to Pro or remove it. How packs work on Free and Pro
How to add a pack
- Download the pack. It is a single file that ends in .promptmason.json.
- In PromptMason, open Settings → Backup & data → Block packs and choose Add a pack from a file….
- Pick the file you downloaded.
The pack is added next to what you have, in a folder named for the pack with one subfolder for each topic. See Add a block pack for the details.
What is inside
Topics
- Technology principles and Phase D scoping
- Baseline technology architecture
- Technology standards catalog and the standards information base
- Technology radar and lifecycle
- End-of-life and obsolescence planning
- Target technology architecture and building blocks
- Technology architecture views and matrices
- Gap analysis and the road to Opportunities and Solutions
- Reference architectures and design reviews
- Technology selection and evaluation
- Platform architecture and platform engineering
- Cloud strategy and landing zones
- Hybrid and multi-cloud workload placement
- Network and connectivity architecture
- Resilience and disaster recovery architecture
- Security architecture at the platform level
- Capacity, cost and FinOps for architecture
- Observability standards
- Technology due diligence in M&A
Technology principles and Phase D scoping
- Role blocks
- Technology architect
- Context blocks
- Company and technology estate, How architecture is done here, Technology principles in force, Scope of this technology architecture work
- Task blocks
- Draft the technology principles, Scope the technology architecture work, Map stakeholder concerns to views, Set the technology taxonomy, Test a proposal against the technology principles
- Format blocks
- Principle statement layout, Scope statement layout, Decision paper
- Constraints blocks
- Work only from the material given, Products are examples, not the architecture, Stay at the architecture level, Use the framework's words, in our own sentences
- Prompts
- Technology principles set; Phase D scope, stakeholders and kick-off; Technology taxonomy for the repository; Principles check of a proposal
- Prompt sets (what is a prompt set?)
- Run Phase D, Technology Architecture. From the scope to the finalized, traced technology architecture: baseline, target, gaps, work packages and the stakeholder review, in order.
- Phase D scope, stakeholders and kick-off
- Baseline portfolio catalog from inventories
- Baseline assessment and write-up
- Target technology architecture description
- Gap analysis
- Gaps to work packages and transitions
- Stakeholder review of the target
- Finalize and trace the technology architecture
Baseline technology architecture
- Role blocks
- Architect documenting the estate
- Context blocks
- Inventory extracts, Domain in focus
- Task blocks
- Discovery questions for infrastructure and platform owners, Baseline technology portfolio catalog from inventories, Reconcile conflicting inventories, Baseline environments and locations, Baseline platform decomposition of a domain, Baseline assessment summary, Baseline technology architecture section
- Format blocks
- Catalog table, Architecture Definition Document section
- Constraints blocks
- The baseline is what runs, not what was intended, Every entry has an owner and a status
- Prompts
- Discovery interview guide; Baseline portfolio catalog from inventories; Where things run; Baseline assessment and write-up
Technology standards catalog and the standards information base
- Role blocks
- Technology standards owner
- Context blocks
- Standards catalog extract, Lifecycle statuses in use
- Task blocks
- Write a technology standard entry, Build the standards catalog from a list, Structure the standards information base, Propose a new technology standard, Review a waiver request against a standard, Annual review of the standards catalog, Retirement notice for a standard
- Format blocks
- Standard layout, Review findings with a verdict, Assessment table with findings
- Constraints blocks
- A standard binds, and says how to depart from it, Every standard has a reason and a review date
- Prompts
- One standard, proposed and written; Standards catalog and its information base; Waiver review; Annual standards review and retirement notices
Technology radar and lifecycle
- Role blocks
- Technology lifecycle owner
- Context blocks
- Technology under assessment, Current radar entries
- Task blocks
- Assess a technology for the radar, Write the radar edition, Trial plan with exit criteria, Lifecycle status definitions and movement rules, Lifecycle review of a technology category
- Format blocks
- Radar entry layout, Radar assessment and trial layout
- Constraints blocks
- A hold is a decision with a date, Judge the technology for this estate
- Prompts
- Radar assessment of one technology; Radar edition; Trial plan; Lifecycle rules and a category review
End-of-life and obsolescence planning
- Role blocks
- Obsolescence planner
- Context blocks
- Vendor support dates and the inventory, Component at risk
- Task blocks
- Obsolescence register from vendor dates and inventory, Risk assessment of an unsupported component, Remediation options for an end-of-life item, Remediation funding paper, Notice to application owners of an end-of-life date, Obsolescence forward look
- Format blocks
- Options comparison, One-page brief for leadership
- Constraints blocks
- Unsupported is a risk with an owner and a date, Classify by business impact, not by technology
- Prompts
- Obsolescence register and forward look; Unsupported component: risk and options; Remediation funding paper; Owner notice of an end-of-life date
- Prompt sets (what is a prompt set?)
- Plan for a technology reaching end of life. From the obsolescence register to the funding paper and the notice to the owners who depend on it, in order.
- Obsolescence register and forward look
- Unsupported component: risk and options
- Remediation funding paper
- Owner notice of an end-of-life date
Target technology architecture and building blocks
- Context blocks
- Target technology architecture, Taxonomy and reference model categories
- Task blocks
- Describe the target technology architecture, Specify an architecture building block, Map building blocks to solution candidates, Target platform decomposition of a domain, Target environments and locations, Target state options and trade-offs, Technology requirements for the requirements specification
- Format blocks
- Building block specification layout, Layered decomposition, Requirements list
- Constraints blocks
- A target choice names the requirement it serves, Building blocks before products
- Prompts
- Target technology architecture description; Building block specified and mapped; Target platforms and locations; Target options paper; Technology requirements
Technology architecture views and matrices
- Context blocks
- Application portfolio extract, Material for the view
- Task blocks
- Application and technology matrix, Environments and locations diagram brief, Platform decomposition diagram brief, Processing diagram brief, Networked computing and hardware diagram brief, Communications engineering diagram brief, View narrative for a stakeholder
- Format blocks
- Matrix layout, Diagram drawing brief
- Constraints blocks
- One viewpoint, one question, one stakeholder
- Prompts
- Application and technology matrix; Environments, locations and platforms views; Processing and hardware views; Communications view and its narrative
Gap analysis and the road to Opportunities and Solutions
- Context blocks
- Baseline and target for comparison
- Task blocks
- Technology gap analysis matrix, Impact of the technology gaps on the other domains, Candidate work packages from the gaps, Transition architectures between baseline and target, Hand-over to Opportunities and Solutions, Stakeholder review talk track for the technology architecture, Finalize the technology architecture
- Format blocks
- Sequenced work table, Talking points for a meeting
- Constraints blocks
- Every gap has a source, A transition state is somewhere you can stay
- Prompts
- Gap analysis; Gaps to work packages and transitions; Hand-over to Opportunities and Solutions; Stakeholder review of the target; Finalize and trace the technology architecture
Reference architectures and design reviews
- Role blocks
- Reference architecture author
- Context blocks
- Design under review, Reference architecture in force, Workload class
- Task blocks
- Write a reference architecture for a workload class, Pattern entry, Compliance assessment against a reference architecture, Infrastructure design review findings, Advice note to a project choosing technology, Refresh a reference architecture, Decide a deviation from a reference architecture
- Format blocks
- Reference architecture document layout
- Constraints blocks
- Review the design, not the author, A finding is graded, and blocking means cannot proceed, Fixed points are few and defended
- Prompts
- Reference architecture for a workload class; Infrastructure design review; Compliance assessment and advice to the team; Refresh a reference architecture
Technology selection and evaluation
- Role blocks
- Technology selection lead
- Context blocks
- Selection requirements and candidates
- Task blocks
- Evaluation criteria and weights from requirements, Long list to shortlist, Scorecard assessment of the candidates, Proof of concept plan, Technology selection recommendation, Technical questions for vendors
- Format blocks
- Evaluation scorecard, Questions list
- Constraints blocks
- Criteria before candidates, Evidence outranks assurance
- Prompts
- Criteria and shortlist; Scorecard; Proof of concept plan and vendor questions; Recommendation paper
- Prompt sets (what is a prompt set?)
- Select a technology. From weighted criteria to the scorecard, the proof of concept and a recommendation a leader can sign, in order.
- Criteria and shortlist
- Scorecard
- Proof of concept plan and vendor questions
- Recommendation paper
Platform architecture and platform engineering
- Role blocks
- Platform architect
- Context blocks
- Platform and its teams
- Task blocks
- Internal platform product definition, Platform capability map, Golden path for a workload type, Platform service catalogue entry, Platform roadmap, Team onboarding plan for the platform, Platform health assessment
- Format blocks
- Platform product definition layout, Golden path walkthrough, Themed roadmap
- Constraints blocks
- The golden path is a default, not a cage, Measure the platform by what teams ship
- Prompts
- Platform product and capabilities; Golden path and its service entry; Platform health and roadmap; Team onboarding to the platform
Cloud strategy and landing zones
- Role blocks
- Cloud architect
- Context blocks
- Cloud providers and footprint, Workloads to migrate
- Task blocks
- Cloud strategy paper, Landing zone design, Hosting and workload placement policy, Migration approach and wave plan, Cloud guardrails standard, Exit and portability position, Cloud responsibility split
- Format blocks
- Design decisions by area, Strategy paper layout, Hosting policy and responsibility layout
- Constraints blocks
- Every placement states residency and exit, Guardrails are enforced, or they are advice
- Prompts
- Cloud strategy; Landing zone design with guardrails; Hosting policy and responsibility split; Migration waves
- Prompt sets (what is a prompt set?)
- Take the estate to the cloud. From the cloud strategy to the landing zone, the hosting policy and the migration waves, in order.
- Cloud strategy
- Landing zone design with guardrails
- Hosting policy and responsibility split
- Migration waves
Hybrid and multi-cloud workload placement
- Context blocks
- Workload to place, Sites and connectivity
- Task blocks
- Placement decision for a workload, Multi-cloud posture options, Concentration risk assessment, Interconnect architecture, Data residency and sovereignty map
- Format blocks
- Posture and portability layout
- Constraints blocks
- Decide by the workload's facts, not the provider's brochure
- Prompts
- Place a workload; Multi-cloud posture and exit position; Concentration risk and residency; Interconnect architecture
Network and connectivity architecture
- Role blocks
- Network architect
- Context blocks
- Network change proposal
- Task blocks
- Network architecture description, Segmentation model and trust boundaries, Connectivity requirements for a new site or workload, Remote access architecture, Network conventions standard, Review a network design change
- Format blocks
- Zones and boundaries layout
- Constraints blocks
- Every flow names both ends and its boundary, No single path for what must not stop
- Prompts
- Network architecture and segmentation; Connectivity requirements; Remote access architecture; Network conventions standard; Network change review
Resilience and disaster recovery architecture
- Role blocks
- Resilience architect
- Context blocks
- Business impact facts, Resilience tiers, System under review
- Task blocks
- Availability tier classification, Resilience patterns and their cost, Disaster recovery architecture for a system, Failure mode analysis of an architecture, Resilience review of a design, Recovery test plan at the architecture level, Map important business services to their technology
- Format blocks
- Analysis table and graded review, Patterns and tier standard layout, Recovery design layout
- Constraints blocks
- Every tier has a price, every pattern has a limit
- Prompts
- Classify systems into tiers; Resilience patterns and the standard; Disaster recovery architecture and test plan; Failure modes and resilience review; Important business services and their technology
- Prompt sets (what is a prompt set?)
- Design resilience and disaster recovery. From resilience tiers to the patterns, one system's recovery architecture and test plan, and the failure mode review, in order.
- Classify systems into tiers
- Resilience patterns and the standard
- Disaster recovery architecture and test plan
- Failure modes and resilience review
Security architecture at the platform level
- Role blocks
- Platform security architect
- Context blocks
- Security framework and controls
- Task blocks
- Platform security principles, Identity and access architecture, Security zones and control points, Secrets, keys and certificates architecture, Platform security baseline, Control mapping to the security framework, Platform threat model, Security architecture review of a design
- Constraints blocks
- Controls map to threats, not to a checklist, The secure way is the default way
- Prompts
- Security principles and zones; Identity, secrets and keys architecture; Baseline and control mapping; Threat model and security review
Capacity, cost and FinOps for architecture
- Role blocks
- Architect who counts the cost
- Context blocks
- Cost and capacity figures
- Task blocks
- Capacity model for a platform, Cost model of a target architecture, Like-for-like cost comparison of options, Cost allocation and showback design, Right-sizing and commitment policy, Cost review of an architecture
- Format blocks
- Cost model table with assumptions
- Constraints blocks
- Costs carry their assumptions and are compared like with like
- Prompts
- Capacity and cost model; Cost review and comparison; Showback design and commitment policy
Observability standards
- Role blocks
- Observability architect
- Context blocks
- Observability tooling and practice
- Task blocks
- Telemetry standard, Observability reference architecture, Service level indicator and objective conventions, Observability tool rationalization, Telemetry retention and cost policy, Observability adoption guidance for teams
- Format blocks
- Telemetry standard layout
- Constraints blocks
- Standards say what to emit, not which tool
- Prompts
- Telemetry standard and service level conventions; Observability reference architecture and retention; Tool rationalization and adoption guidance
Technology due diligence in M&A
- Role blocks
- Technology due diligence lead
- Context blocks
- Deal and target, Data room material
- Task blocks
- Technology diligence request list, Technology estate assessment from the data room, Diligence findings report, Integration options for the two estates, Day-one and transition service dependencies, Technology integration roadmap, Questions for the management sessions
- Format blocks
- Diligence findings layout
- Constraints blocks
- Findings are evidence, not opinion
- Prompts
- Request list and management questions; Estate assessment and findings report; Integration options and day one; Technology integration roadmap
- Prompt sets (what is a prompt set?)
- Technology due diligence and integration for a deal. From the data room request list to the findings, the integration options and the integration roadmap, in order.
- Request list and management questions
- Estate assessment and findings report
- Integration options and day one
- Technology integration roadmap