Technology Governance Writer (Bank)

MNC|Bank

Contract Duration: 6 months
Location: Changi Business Park, Singapore
Industry: Banking / Financial Services

Role Purpose

A leading financial institution is looking for a Technology Governance Writer to support Group Technology in developing a new Project Management Standard (PjMS) and updating the existing Platform Management Standard (PMS).

The role will coordinate with Lines of Business Technology (LOBTs), subject matter experts, governance functions and document owners to understand current project and platform management practices, identify common and differing requirements, and translate the findings into clear, consistent and enforceable Group Technology Standards.

The writer will consolidate information from stakeholder discussions, existing policies and standards, audit observations, current operating practices, regulatory expectations and recognised project-management frameworks. The resulting documents must be draft-ready for stakeholder review and comply with the required standards structure, formatting and documentation conventions.

Key Responsibilities

Stakeholder Engagement and Coordination

• Plan and coordinate structured discussions with LOBTs and relevant Group Technology functions.
• Interview project, programme, Platform, governance, risk and control subject matter experts.
• Document current project and Platform management practices, artefacts, systems, roles and governance arrangements.
• Identify common practices, material variations and unresolved requirements across LOBTs.
• Organise follow-up discussions to validate findings and close information gaps.
• Maintain stakeholder comments, decisions, open questions and required approvals.
• Prepare concise materials to support working sessions and management reviews.

Standards and Requirements Analysis

• Review existing mandates, policies, standards, guides, procedures, templates and supporting artefacts.
• Analyse audit observations and management actions relevant to Platform and project management.
• Review recognised project-management practices and authorised external frameworks, including Project Management Book of Knowledge (PMBOK), where applicable.
• Identify requirements relating to governance, scope, planning, schedule, cost, resources, risk, quality, benefits, transition and closure.
• Distinguish mandatory requirements from guidance, implementation practices and explanatory content.
• Identify duplicated, conflicting, outdated or missing requirements.
• Determine whether content belongs in the PMS, PjMS or a supporting Guide.
• Maintain clear traceability between each proposed requirement and its source.

Technical Writing and Editing

• Translate complex technical, governance and risk information into clear language.
• Write consistently for Technology practitioners, project teams, Platform roles, governance bodies, risk functions and approvers.
• Apply appropriate normative language to distinguish mandatory requirements from recommendations.
• Define technical and governance terms consistently.
• Improve document structure, readability and logical flow.
• Edit content for clarity, conciseness, accuracy and internal consistency.
• Verify references, terminology, cross-references, numbering and defined terms.
• Proofread all outputs before stakeholder circulation.
• Develop tables, diagrams or structured summaries where these improve comprehension.

Traceability and Review Management

• Maintain a clause-level requirements and source traceability register.
• Record the source, rationale, owner and validation status of proposed clauses.
• Track comments from LOBTs, SMEs, Risk, Finance, Audit and other reviewers.
• Consolidate overlapping comments and highlight conflicting stakeholder positions.
• Maintain decision logs and clearly identify matters requiring management direction.
• Update drafts following agreed decisions without losing source traceability.
• Prepare before-and-after views for materially changed requirements.
• Track review comments through resolution or formal deferral.

Quality Assurance and Handover

• Perform completeness and consistency reviews across the PMS and PjMS.
• Confirm that the proposed requirements are understandable, testable and evidence-based.
• Check alignment between requirements, roles, artefacts, governance forums and exception processes.
• Identify any remaining drafting assumptions, information gaps or unresolved decisions.
• Prepare draft-ready Standards for formal stakeholder review and approval.
• Organise source materials, interview notes, traceability records and review logs for handover.
• Provide recommendations for maintaining the Standards after the engagement.
• Support knowledge transfer to the document owners and internal team.

Project Management Standard Authoring

• Develop the structure and detailed content of the new PjMS.
• Define its purpose, scope, applicability, exclusions and key terms.
• Draft requirements for Tech-led Build project governance and lifecycle management.
• Translate approved requirements into clear, concise and enforceable clauses.
• Define roles, responsibilities, approvals, governance forums and escalation expectations.
• Draft requirements for project classification, initiation, planning, execution, monitoring, control, transition and closure.
• Address proportionality and tailoring based on approved criteria such as project risk, complexity and materiality.
• Document mandatory project artefacts, decisions, approvals and evidence requirements.
• Ensure the PjMS supports consistent implementation while accommodating approved delivery methodologies and LOBT contexts.

Platform Management Standard Revision

• Review the existing PMS clause by clause.
• Identify obsolete, ambiguous, duplicated or project-specific content.
• Retain and strengthen requirements supporting the Platform Operating Model.
• Update Platform governance, financial governance, benefits tracking, oversight and related Platform management requirements.
• Move project-specific requirements to the PjMS where approved.
• Draft appropriate cross-references between the PMS and PjMS.
• Ensure that separating the Standards does not introduce control gaps, conflicting obligations or unnecessary duplication.
• Maintain alignment with the related Group Technology Risk Management Policy and other applicable internal documents.

Skills and Experience

Essential

• Strong experience in technical writing, policy writing, standards authoring or governance documentation.
• Demonstrated ability to translate complex operating practices into clear and structured requirements.
• Experience developing or updating policies, standards, procedures, controls or governance frameworks.
• Strong stakeholder-engagement and workshop-facilitation abilities.
• Ability to interview technical and non-technical SMEs and consolidate differing viewpoints.
• Strong writing, editing, proofreading and document-structuring skills.
• Experience maintaining source-to-requirement or clause-level traceability.
• Ability to distinguish mandatory controls from guidance and explanatory content.
• Strong attention to detail, version control and document consistency.
• Proficiency in Microsoft Word, Excel and PowerPoint.
• Ability to work independently across multiple stakeholder groups and manage concurrent review cycles.

Preferred

• Experience within banking, financial services or another regulated industry.
• Knowledge of technology governance, technology risk or IT project delivery.
• Familiarity with Platform operating models and project-management governance.
• Understanding of Agile, Waterfall and hybrid delivery methodologies.
• Familiarity with PMBOK or comparable project-management frameworks.
• Experience working with audit findings, regulatory expectations or control frameworks.
• Experience writing documents intended for formal approval and controlled publication.
• Familiarity with policy-management repositories.
• Experience working with Group-level and country-level stakeholders.
• Ability to interpret existing governance practices without automatically converting every practice into a mandatory requirement.

Education

• Bachelor's degree in technical communication, English, communications, information systems, engineering, computer science, business, project management or a related discipline.
• Relevant qualifications in technical writing, business analysis, project management, risk management or governance would be advantageous.
• PMP, PRINCE2, IIBA, ITIL, COBIT or equivalent credentials are advantageous but not mandatory.

Next Steps

• Drop your resume and contact us to follow-up, or send your resume to amos.tan@adecco.com
• Email Topic: Apply Technology Governance Writer
• Only shortlisted candidates will be contacted

Amos Tan Jun Han

EA License No: 91C2918
Personnel Registration Number: R23113385