Planning your development with SFIA

You do not need to understand the whole framework before you start. It is usually more useful to choose one or two areas to focus on, then look for practical opportunities to practise them and collect examples.

Your development goals might relate to:

• a professional skill you want to practise
• a behaviour you want to strengthen
• a type of work you want to explore
• a gap you have noticed in your experience
• feedback from a tutor, supervisor, mentor or employer
• a role or career area that interests you.

The aim is not to create a long list of things to improve. A small number of focused goals is usually easier to act on and review.

Start from where you are

Development planning works best when it starts with real evidence.

Before choosing a goal, look at what you have already done. This might include coursework, projects, volunteering, part-time work, student societies, placements, internships, apprenticeships or personal projects.

Ask yourself:

• what have I done recently?
• what did I personally contribute?
• what went well?
• what was difficult?
• what feedback did I receive?
• what did I avoid because I lacked confidence or experience?
• what would I like to be better prepared for next time?

This helps you choose a goal that is grounded in your current experience.

Use SFIA to identify development areas

SFIA can help you think about development from different angles.

You might look at:

Development angle	SFIA can help you ask
Professional skills	What kind of work am I interested in or beginning to practise?
Behavioural factors	How do I work with others, communicate, plan, solve problems and learn?
Generic attributes	How much independence, influence and complexity am I ready for?
Knowledge	What do I need to understand better to contribute effectively?
Evidence	What examples can I use to describe my development?

For many students, behavioural factors and generic attributes are a good starting point. You may already have evidence of collaboration, communication, planning, problem-solving, adaptability, learning and development, digital mindset, or security, privacy and ethics.

You can then connect these behaviours to professional skills as your experience grows.

Choose one or two development goals

A useful development goal should be specific enough to act on.

Instead of:

I want to improve my communication.

try:

I want to become more confident explaining technical work to people who are not familiar with the details.

Instead of:

I want to get better at coding.

try:

I want to practise writing clearer, tested and documented code for small features.

Instead of:

I want to be more professional.

try:

I want to ask for guidance earlier when a task is unclear, rather than waiting until I am stuck.

Each goal should help you decide what to practise and what examples to record.

Use a simple development cycle

You can use a simple cycle to plan and review your development.

1. Explore

Look at SFIA skills, behavioural factors or levels that relate to your interests or current experience.

You might explore:

• a professional skill linked to a career area
• a behaviour you want to strengthen
• a level of responsibility you want to understand
• feedback from a project, placement or supervisor.

2. Choose

Select one or two areas to focus on.

Try not to choose too many goals at once. Development is easier to manage when the next step is clear.

3. Practise

Look for opportunities to apply the skill or behaviour.

This might be in:

• coursework
• group projects
• presentations
• labs
• volunteering
• part-time work
• student societies
• placements
• internships
• personal projects
• conversations with tutors, supervisors or mentors.

4. Record

Keep a short record of what happened.

Include:

• what you did
• who you worked with
• what guidance or feedback you used
• what problems or uncertainty you faced
• what changed as a result
• what you learnt.

5. Review

After a few weeks, review your progress.

Ask:

• what examples have I recorded?
• what has improved?
• what still feels difficult?
• what feedback have I received?
• should I continue with this goal, adjust it or choose a new one?

This does not need to be a formal process. A short note every few weeks can be enough.

Find opportunities to practise

Once you have chosen a development goal, look for situations where you can practise it.

Development goal	Possible opportunities
Communicate more clearly	presentations, project updates, documentation, explaining work to classmates or colleagues
Collaborate more effectively	group projects, societies, volunteering, workplace tasks, peer review
Plan and track work	coursework deadlines, project plans, digital task boards (like Trello or Jira), placement objectives
Solve problems methodically	labs, debugging, data analysis, research tasks, process improvements
Learn and apply new knowledge	independent study, tutorials, feedback, new tools or methods
Use digital tools responsibly	research, data handling, AI tools, documentation, tracking changes to your code or files (version control)
Understand user or customer needs	project briefs, interviews, service tasks, feedback sessions
Raise issues earlier	project check-ins, supervisor meetings, team updates, placement reviews

You may not control all the opportunities available to you. That is normal. Use the opportunities you do have, and ask for others where appropriate.

Turn goals into practical actions

A development goal becomes more useful when it is linked to action.

Goal	Practical action
Improve planning	Create a simple task list before starting the next project and review it weekly
Improve communication	Ask someone unfamiliar with the topic to read a short explanation and give feedback
Improve collaboration	Agree responsibilities at the start of a group task and check progress regularly
Improve problem-solving	Record what you tried before asking for help
Improve learning from feedback	Choose one piece of feedback and show how you applied it
Improve digital mindset	Learn one tool feature that improves how you complete a task
Improve security, privacy and ethics	Check the rules before using personal data or AI tools

These actions are small, but they help turn development into practice.

Use SFIA levels carefully

SFIA levels describe responsibility, not just difficulty.

A technically difficult assignment does not automatically show a high level of responsibility. A simple workplace task may involve real users, real consequences or important judgement.

When planning development, use the levels to understand how responsibility changes.

At early levels, this may mean moving from:

• following instructions, to planning your own short-term work
• asking for guidance in unexpected situations, to deciding when guidance is needed
• working mainly on your own task, to contributing to team discussions
• resolving routine issues, to using a methodical approach for more complex issues
• applying newly acquired knowledge, to identifying your own development opportunities.

You do not need to assign yourself a SFIA level. It is often enough to use the levels to ask better questions about your development.

Prepare for development conversations

SFIA can help you have more useful conversations with people supporting your development.

This might include:

• tutors
• careers advisers
• placement supervisors
• line managers
• mentors
• apprenticeship advisers
• project supervisors.

Before a conversation, prepare a short summary.

What I have done

Describe one or two specific examples.

I worked on the charts and graphs (data visualisation) part of our group project. I prepared the first version, received feedback that it was difficult to interpret and changed the layout before the final presentation.

What I think it shows

Link the example to behaviours or skills.

This shows communication, learning from feedback and using digital tools. It may also relate to data analysis, depending on how the work is interpreted.

What I want to develop next

Choose one or two focused goals.

I want to get better at explaining data insights clearly to non-specialist audiences.

What support or opportunity would help

Be specific.

I would like to present a short update in our next project meeting and get feedback on whether the key message is clear.

This kind of preparation makes it easier for others to support you.

Example: developing communication

Starting point

I find it difficult to explain technical work clearly to people outside my course.

SFIA link

This relates to communication. At early levels, SFIA describes listening, asking questions, sharing information and explaining information clearly to teams and stakeholders.

Development goal

I want to explain technical work more clearly to non-specialist audiences.

Practice opportunity

In my next project, I will write a short summary of what the system does, why it matters and what decisions need to be made.

Examples to keep

I will keep the first version, feedback received and the revised version.

Review question

Did the revised version make the main message clearer?

Example: developing problem-solving

Starting point

When something does not work, I sometimes try random fixes rather than recording what I have tried.

SFIA link

This relates to problem-solving. At early levels, SFIA describes seeking assistance with unexpected problems, resolving routine issues and applying a methodical approach.

Development goal

I want to use a more methodical approach when solving technical problems.

Practice opportunity

For the next debugging task, I will record the error, the likely causes, what I tested and what changed.

Examples to keep

I will keep my notes and describe how they helped me decide what to do next.

Review question

Did recording the steps help me solve the problem or ask for better guidance?

Example: developing collaboration

Starting point

In group work, I sometimes focus only on my own section and do not check how it fits with the rest of the project.

SFIA link

This relates to collaboration and influence. At early levels, SFIA describes understanding how your work supports others, contributing to team discussions and working with team decisions.

Development goal

I want to contribute more effectively to shared outcomes in group work.

Practice opportunity

At the start of the next group project, I will agree how my task connects to others and check progress with the group each week.

Examples to keep

I will note what was agreed, what changed and how I adapted my work.

Review question

Did my contribution help the group’s overall result, not only my own task?

Keep your development record manageable

A development record does not need to be long.

For each goal, you might keep one short note every few weeks:

• Date
• Goal
• What I practised
• Evidence
• What I learnt
• Next step

This can help you prepare for:

• applications
• interviews
• placement reviews
• portfolio work
• personal tutor meetings
• careers appointments
• professional development conversations.

The value is in the reflection, not the size of the record.

Use SFIA as a guide for growth

SFIA can help you notice what you are developing and plan what to practise next.

It can help you:

• choose development goals
• find opportunities to practise
• collect better evidence
• prepare for conversations
• connect academic work with professional expectations
• understand how responsibility grows over time.

Start small. Choose one area, practise it deliberately, record what happened and use the evidence to decide your next step.