You’re working on a task that involves handling sensitive data. The company has a documented procedure for how to process and store this information, including a required approval in your workflow tool. You’re under time pressure and could finish faster by skipping a couple of steps. What should you do?, Skip the extra steps for now and handle everything more thoroughly later if someone brings it up, assuming it won’t create issues in the meantime., Follow the documented procedure end-to-end, completing the needed documentation and getting the required approval in the tool., Ask a peer what they typically do in similar cases and follow that practice, even if you know it doesn’t completely align with the official process., You notice a recurring bottleneck: different teams frequently ask the same questions because a policy change was announced but the guidance is scattered across emails and chats. This causes delays and duplicate work across the company. What should you do?, Assume that things will naturally settle over time and that people will eventually adapt without you needing to get involved., Publish your own version of the rules immediately to try to eliminate confusion, even if you haven’t aligned with the teams involved., Gather the recurring questions and recommend creating a simple, centralized FAQ or reference guide, sharing it with your manager and stakeholders for review., You’re preparing a status update for stakeholders. You realize a key deliverable is behind schedule due to an oversight that you were involved in. You can frame the delay as an external dependency or present the facts as they are. What should you do?, Share the facts clearly, acknowledge your part in the delay, and outline how you plan to get the work back on track., Refer to the delay as the result of other teams or external blockers so you don’t have to address uncomfortable questions about your role in it., Leave the delay out of your update for now and hope the issue resolves itself before anyone asks about it., You identify a low-risk idea that could streamline a routine task (e.g., a template, checklist, or simple automation) and save time for multiple teams. No one asked for it, but the potential benefit is clear. What should you do?, Keep the idea to yourself since introducing improvements doesn’t fall directly under your defined responsibilities., Test the idea on a small scale, gather evidence of its impact, and propose broader adoption through the proper channels., Start rolling out the new method to all teams on your own because you're confident it will be useful to everyone., A colleague provides feedback that your recent handoff lacked clarity and caused rework for their team. You’re busy and feel the feedback is poorly timed, but the next handoff is coming up soon. What should you do?, Acknowledge the feedback respectfully, clarify what would help, and adjust your handoff template or checklist for the next delivery., Push back on the feedback by explaining why their expectations are unrealistic and why your approach made sense., Set the feedback aside and continue with your usual process to avoid adding more tasks to your workload right now.

FTO Values - L2A2 (DRAFT)

by
Print
Embed

Leaderboard

Visual style

Options

Switch template

Continue editing: ?