Agree the scope before the activity
Before work begins, the reason, objective, timeframe, available material and decision points are recorded. Work may include reviewing documents, preparing important conversations or assessing a technical issue for a board decision. Anything not agreed is not silently added to scope.
- Two to four days of work per month.
- Engagements in agreed three-month blocks.
- External judgement and support, not operational programme leadership.
Useful where several parties shape the decision
The format may suit a partner negotiation, technical due diligence or an audit-readiness decision. Nearshore experience includes teams grown from 5 to 150 people and eight development centres running at once. That is relevant context, not an offer to take over day-to-day provider management.
Not an implementation mandate
The current service is not general implementation or operational team management. Jürgen Röck does not assume a corporate office or ownership of the initiative's outcomes. Technical judgement, agreed support and explicit boundaries belong together.
A considered next step
Clarify the question before choosing the scope.
An initial conversation is for clarifying the issue, the available information and the boundaries. If another format is a better fit, that will be said plainly.