Pros
The team is generally close-knit and helpful, making it relatively easy to build good working relationships.
Exposure to a range of public sector projects provides experience in working within structured guidelines and stakeholder requirements.
The pantry is occasionally stocked, providing small perks that contribute to a more comfortable working environment.
Cons
There is often a lack of clear direction across projects, with multiple stakeholders providing input and frequent last-minute changes, at times even hours before submission. This creates unnecessary pressure and makes it difficult to manage timelines effectively. Involvement is often centred on execution, with less exposure to the earlier stages of project development.
There can be a tendency towards close oversight of work, with limited autonomy at times, which may impact trust and ownership.
Support for upskilling is limited, particularly in keeping up with evolving software and tools. Devices and software are not always up to date, and upgrade requests are often constrained by budget, despite the scale and pace of work.
Resourcing is lean, and with account servicing teams operating remotely, communication gaps can affect project alignment. While SOPs are regularly emphasised, they are not consistently followed in practice.
Meetings do not always start on time, including client-facing ones, which can impact professionalism and respect for schedules. There is also a recurring expectation to work beyond regular hours, including weekends, with limited formal structure around compensation or recognition. Therefore, there is a lack of work-life balance.
There is no clear studio or workflow management in place, which contributes to inefficiencies and disorganisation. Team culture can at times feel political, with instances of gossip and behaviour that may affect team cohesion.
Flexible working arrangements are offered, but there can be some resistance when they are utilised, making the policy feel less consistent in practice.