Spaces:
Runtime error
Runtime error
| # SFIA Role Guidance: Associate Designer | |
| * [SFIA Level 2](https://sfia-online.org/en/legacy-sfia/sfia-7/responsibilities/level-2) | |
| * [Job description](../associate_designer.md) | |
| ## Summary of role | |
| Associate Designers are practitioners who collaborate with others to tackle challenges faced by people and society. They work within a team to design and deliver public services. They do this by understanding problems and creating solutions that work for equally well for users and stakeholders. They are active members of a healthy User-Centred Design (UCD) community and culture at Made Tech. | |
| ## Required competency for the role | |
| ### Autonomy | |
| * Works under routine direction. | |
| * Uses limited discretion in resolving issues or enquiries. | |
| * Works without frequent reference to others. | |
| #### Examples behaviours and responsibilities | |
| _Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ | |
| * Carries out clearly define tasks within a design sprint. | |
| * Can piece together a flow of online form and seeks feedback from others after first attempt. | |
| * Can demonstrate a prototype | |
| * Can begin to apply GOV.UK Design System to basic forms and page layouts. | |
| --- | |
| ### Influence | |
| * Interacts with and may influence immediate colleagues. | |
| * May have some external contact with customers, suppliers and partners. | |
| * May have more influence in own domain. | |
| * Aware of need to collaborate with team and represent users/customer needs. | |
| #### Examples behaviours and responsibilities | |
| _Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ | |
| * Assists UCD people in a team to get ready for user testing. | |
| * Can prototype in more than one way if asked. | |
| * Understands they need to collaborate with software engineers if they are design services that actually get built. | |
| --- | |
| ### Complexity | |
| * Performs a range of work activities in varied environments. | |
| * May contribute to routine issue resolution. | |
| #### Examples behaviours and responsibilities | |
| _Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ | |
| * Sketches design ideas to a problem that’s well defined by user research. | |
| * Leads certain activities as part of a discovery kick-off with support from more senior teammates. | |
| * Corrects typos and other small errors in prototypes before and during testing with users. | |
| --- | |
| ### Knowledge | |
| * Demonstrates application of essential generic knowledge typically found in industry bodies of knowledge. | |
| * Has gained a basic domain knowledge. | |
| * Absorbs new information when it is presented systematically and applies it effectively. | |
| #### Examples behaviours and responsibilities | |
| _Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ | |
| * Applies the 'one thing per page' principle to their prototypes. | |
| * Can spot basic accessibility issues in an existing service. | |
| * Applies the basics of storytelling to talk about their own design career so far. | |
| --- | |
| ### Business Skills | |
| * Has sufficient communication skills for effective dialogue with customers, suppliers and partners. | |
| * Is able to work in a team. Is able to plan, schedule and monitor own work within short time horizons. Demonstrates a rational and organised approach to work. | |
| * Understands and uses appropriate methods, tools and applications. | |
| * Identifies and negotiates own development opportunities. | |
| * Is fully aware of and complies with essential organisational security practices expected of the individual. | |
| _Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ | |
| * Produces prototypes without pairing or instructions. | |
| * Checks in with teammates everyday to ensure they’re not working in a silo or diverging from team goals. | |
| * Offers to support teammates when priorities change, seeing teammate meets goals rather than just their individual ones. | |
| * Communicates when their work is being blocked and maybe who they need to work with to change that. | |