Skip to main content

Organisational readiness survey

Purpose. A short instrument, issued to a cross-section of staff, that establishes the organisational starting point. Answers are aggregated; individuals are not identified.

Respondent details​

FieldDetail
Department
Role levelIndividual / team lead / manager / executive
Tenure< 1 year / 1–3 years / 3+ years
Optional: name

01 — Organisational culture​

  1. How would you describe the overall culture?

    • Hierarchical and siloed
    • Collaborative and innovative
    • Inflexible and resistant to change
    • Other:

  2. How encouraged do you feel to share ideas and feedback within your team?

    • Very encouraged
    • Somewhat encouraged
    • Not encouraged
    • Unsure

  3. How would you rate trust and transparency between departments?

    • High
    • Moderate
    • Low
    • Not applicable

  4. When something fails, the response is:

    • Blame
    • Problem-solving
    • Both, depending on the team
    • Unsure

02 — Team structure​

  1. How are teams structured in your area?

    • Traditional functional teams (development, testing, operations)
    • Cross-functional teams with shared responsibility
    • Other:

  2. Does the current structure facilitate collaboration?

    • Yes, to a great extent
    • Yes, to some extent
    • No, not really
    • Unsure

  3. Who owns a service after it is deployed?

    • The development team
    • The operations team
    • Shared
    • No clear owner

03 — Communication​

  1. Which channels are used for intra-team communication? (Select all)

    • Email
    • Instant messaging (Slack, Teams)
    • In-person meetings
    • Project management tools (Jira, Trello)
    • Other:

  2. How effective are those channels for collaboration and information sharing?

    • Very effective
    • Moderately effective
    • Ineffective
    • Unsure

  3. How do you find out about decisions that affect your work?

    • Formally communicated
    • Through meetings
    • Through colleagues
    • Often too late

04 — Workflow and process​

  1. How would you describe the current software delivery lifecycle?

    • Waterfall (sequential)
    • Agile (iterative)
    • Hybrid
    • Other:

  2. Are automated testing and deployment used in your team?

    • Yes, extensively
    • Yes, to some extent
    • No
    • Unsure

  3. How long does a routine change take from approval to production?

    • Same day
    • Within a week
    • 1–4 weeks
    • More than a month

  4. What is the most common reason a change is delayed?

05 — Skills and training​

  1. Do you feel equipped with the skills to adopt DevOps practices?

    • Fully equipped
    • Partially equipped
    • Not equipped
    • Unsure

  2. Have you received formal training on cloud or DevOps?

    • Yes, extensively
    • Yes, to some extent
    • No
    • Unsure

  3. What training would help you most?

06 — Leadership and change​

  1. How often does leadership discuss delivery performance?

    • Regularly, with data
    • Occasionally
    • Rarely
    • Never

  2. Have you experienced a previous improvement initiative?

    • Yes, and it succeeded
    • Yes, and it did not last
    • Yes, and it failed
    • No

  3. What would make this initiative different?

07 — Additional feedback​

  1. What are the three biggest obstacles to doing your best work?
  2. What should change first?
  3. Anything else we should know?

Analysis (completed by the assessor)​

AreaScore 1–5EvidenceConstraint identified
Culture
Team structure
Communication
Workflow
Automation
Skills
Leadership

Overall readiness profile:

Top three constraints:

Recommended sequencing: