Resources
SAP SuccessFactors + riteful: development throughout the year
Agree goals in January, assess them in December: how SAP + riteful supports development in between. A comparison across the full year.
MarkusIn January, Nora and her manager agree on a goal in SAP SuccessFactors: by the end of the year, Nora will independently lead a defined part of a project. In December, they assess whether she has achieved it. The result may also inform a salary discussion or bonus.
The crucial question lies between those two meetings: how will Nora be supported in reaching the goal throughout the year? The goal agreement records the expectation. The annual review assesses the result. In the intervening months, she needs concrete assignments, feedback, support and the opportunity to adjust her development path.
This is where riteful complements an SAP process centered on annual goal setting and reviews. SAP remains the framework for goal agreements and assessment. With riteful, development is actively supported throughout the year. Managers and employees keep working towards the goal, discuss experiences and agree on next steps. Synchronization in both directions connects this development work with the designated goal data in SAP.
SAP as the framework for goals, assessment and compensation
Goal agreements need a shared point of reference. SAP SuccessFactors can hold goals with deadlines, status, progress and weighting, among other fields. The weight can also feed into the performance form.
This formal framework is particularly relevant when a performance assessment subsequently informs compensation. SAP SuccessFactors Compensation supports salary planning and can use ratings from Performance Management. Variable Pay supports bonus processes that can incorporate business, team and individual goal results. The actual connection depends on the modules in use and the organization's compensation model.
For organizations that already run these processes in SAP, a clear division of responsibilities is possible: goal agreements, formal assessments and compensation-relevant documentation remain anchored there. riteful supports development between goal setting at the start of the year and assessment at the end. HR can continue its existing process while managers and employees gain a workspace focused on execution.
01 · How the systems work together
Goals in SAP. Execution in riteful.
SuccessFactors- Goals & criteria
- Performance assessment
- Compensation processes
Depending on modules and compensation model
Development throughout the year- PlanAgree on steps together
- ObserveRecord experiences
- DiscussProvide support as needed
- Follow throughRevisit agreed actions
SAP vs. SAP + riteful: what happens between January and December
This comparison considers an SAP process anchored in goal setting at the start of the year and assessment at the end. Development support between those milestones has to be organized separately. Adding riteful makes that period a continuously supported part of everyday leadership.
02 · SAP vs. SAP + riteful
One annual goal. Two approaches.
SAP
- JanuaryAgree on the goal
- February – NovemberOrganize support separately
- DecemberAssess the goal
SAP + riteful
- JanuaryAgree on the goal
- February – NovemberOngoing developmentPlan · Discuss · Follow through
- DecemberAssess the goal
| Across the year | SAP in the annual process described | SAP + riteful |
|---|---|---|
| Start of the year | Agree on goals, success criteria and timeframe in SAP | The same goal agreement in SAP; jointly translate it into a development plan in riteful |
| During the year | Organize assignments, feedback and conversations separately between the formal milestones | Turn goals into practical steps, proactively gather conversation needs and support development throughout the year |
| When progress stalls or circumstances change | Address obstacles and adjustments through separately organized conversation routines | Connect current topics with the plan, clarify support and follow through on next steps |
| End of the year | Assess goal attainment in SAP and, where applicable, use it in compensation processes | The same formal assessment in SAP, with designated goal updates from development supported throughout the year |
SAP SuccessFactors also offers ongoing conversation and feedback capabilities through Continuous Performance Management. The comparison here is between the annual process described and the additional support provided by riteful. For this starting point, the key value is connecting the annual goal with continuous development in everyday work.
How riteful supports development throughout the year
New assignments, experiences and obstacles emerge between January and December. The annual goal needs to be translated into current work as the year unfolds. A useful operational layer connects those decisions with the goal: What will we try, what will we learn from it and what will we do next? riteful brings planning, observations and conversations together in an ongoing workflow.
If this work is currently spread across chat threads, calendar events and individual notes, the manager has to reconstruct the connections before each conversation. riteful brings the shared plan, current conversation needs and previous agreements into one workflow. The existing goal agreement in SAP becomes the basis for ongoing support.
1. Turn the agreed goal into a shared working plan
A goal such as “take on more project responsibility” sets a direction. Execution requires suitable assignments, a realistic timeframe and support. In riteful, managers and employees jointly translate the annual goal into a development and conversation plan. They define suitable stages and adapt the plan as the year progresses.
For Nora, this becomes a concrete sequence: first prepare a project meeting, then facilitate it herself and subsequently follow up on decisions and outstanding items with the participants. Her manager clarifies which decisions Nora may make independently and where she needs backing.
The value: the goal gains an actionable path. Both people can discuss which step makes sense now, who will contribute and which experience they will review in the next one-on-one. Role expectations and skills provide additional context; our article on roles and structured occupational data explores this further.
2. Gather conversation needs proactively
A development plan needs attention while the work is happening. riteful proactively gathers topics and conversation needs and plans the timing and agenda accordingly. The shared plan, current topics and issues requiring clarification give the conversation a concrete purpose.
If Nora is stuck waiting for approval, the relevant question is what support she needs now. If a step has gone well, the conversation can address the next challenge. The manager therefore does not have to assemble conversation needs solely from memory and incidental comments.
The value: support remains a priority throughout the year. Employees can bring up their concerns, and managers receive a prepared connection to the agreed development path. The annual goal stays part of the dialogue in spring, summer and autumn.
3. Use work experiences as conversation context
A goal status rarely explains on its own why something is working or getting stuck. riteful connects development work with specific observations. These can be recorded directly in the journal or brought in from connected work systems such as Microsoft Teams and Jira, then linked to skills, accountabilities and goals.
“Before the meeting, Nora collected the outstanding decisions and identified who was responsible for each” is a specific starting point. Both people can consider what was helpful and what feedback Nora received from the participants. They can also explore whether an obstacle concerns her skills, unclear responsibilities or missing resources.
The value: conversations can start from actual work situations. AI-assisted agenda creation brings together goals, current topics, outstanding actions and previous conversation context. People review the interpretation and add their perspectives. Our article on recording observations explains how to keep observations separate from interpretations.
4. Revisit agreements as the work continues
A good conversation ends with an agreement that needs to be acted on. riteful supports summaries and next steps and connects them with subsequent conversations. The next agenda can build on outstanding items and earlier discussions.
For Nora, this might mean that her manager takes responsibility for resolving an approval while Nora prepares the next project meeting. In their following conversation, they review what happened and whether the development plan needs to change.
The value: development remains connected across months. The contributions agreed by both people remain part of the dialogue. AI helps organize and summarize information; managers and employees remain responsible for the content and decisions. We discuss the role of AI in employee conversations in a separate article.
Example: supporting an annual goal over twelve months
Nora's January goal remains the point of reference throughout the year. The following stages show how riteful supports her development along the way. The example assumes that the goal and updates are included in the configured synchronization scope. Conversations take place according to need; the months are illustrative.
January: agree on the goal in SAP. Nora is expected to lead a defined part of a project independently by December. Criteria, timeframe and any compensation relevance are recorded in the existing HR process. In riteful, Nora and her manager plan which assignments she will begin with and what support she needs.
Spring: review early experiences together. Nora takes on smaller project meetings. In the one-on-ones supported by riteful, they discuss what went well and where she still feels uncertain. Each conversation leads to a next assignment, and subsequent conversations revisit her experiences with it.
Summer: resolve obstacles and adjust the plan. An approval falls outside Nora's authority. Her manager takes responsibility for resolving it. If the project scope or priorities change, they adapt the next development steps. Any necessary change to the formal annual goal is agreed through the designated SAP process.
Autumn: support the next step in responsibility. Nora takes on a larger part of a project. riteful connects her current topics with previous agreements and the development plan. Together, they consider which tasks she can already handle independently and where further support would help.
December: assess goal attainment in SAP. The designated goal updates are written back to SAP. Formal assessment follows the agreed criteria. The annual result now follows months of supported development through assignments, feedback and obstacles addressed together.
The value is created during the year: Nora receives support while she can still shape her path towards the goal. Her manager accompanies that process throughout. This is an illustrative workflow, not a measured customer success story.
What flows back into SAP
Bidirectional synchronization connects the two workspaces. The goal and context data involved, and the updates to be written back, are defined for the connection. SAP provides read and write interfaces for this purpose; available data objects and fields can be checked against the particular configuration.
Formal goal attainment and its possible compensation relevance continue to be assessed through the designated process. A completed development step in riteful is not, on its own, a final performance assessment. Salary and bonus decisions remain with the responsible people and established HR processes.
Confidential development work also needs a clear boundary from formal documentation. In riteful, HR can see whether one-on-ones take place but cannot access conversation content or private notes. The agreed write-back must respect this separation. Our guide to a privacy- and works-council-friendly rollout covers the organizational framework.
Assess the value through your own goal process
Take an annual goal already agreed in SAP and consider the period until the next assessment: Who translates it into practical steps? How does the need for support become visible? Which experiences reach the next conversation? And how are agreements followed through?
This is the work riteful supports as an operational layer: structuring development between annual reviews and supporting the participants as they work towards their goals throughout the year. In a demo, we can show how the systems work together around your goal agreements, conversation routines and intended data exchange with SAP SuccessFactors.