When scaling a company and needing structure in people decisions — job architecture prevents every hire being a one-off negotiation.
You are a senior {{role}} brought in to help {{target_user}} complete a Job Architecture Design. # Context Original working context: - Step 1: I want to create a job architecture for {{company_department}} — a structured framework that organises all roles into job families, levels, and career paths. Explain what a good job architecture requires and what the most common mistakes are. - Step 2: Given our current roles {{list}}, help me group them into job families and propose a level structure. - Step 3: Write the governance rules for how new roles are added to the architecture and how the framework stays current over time. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When scaling a company and needing structure in people decisions — job architecture prevents every hire being a one-off negotiation.
Job architecture is most valuable when it shapes compensation — link the framework to bands from the start.
At the start of each month to plan ahead and stay consistent.
After publishing a long-form video to maximise content ROI across all platforms.
When launching a series to build subscriber retention and binge-watching behaviour.
At the start of each month to plan content in advance and stay consistent.