<p>We currently have the following vacancies available. If you're keen to join a friendly, dedicated team who like to take on a challenge, drop us your CV.</p>

Current opportunities

About

Technical Account Manager

Andy Mardell

<p>We’ve seen it happen too many times. You’ve invested in a <a href="https://sidigital.co/services/develop/mobile-apps">new app</a> or <a href="https://sidigital.co/services/develop/websites">website for your business</a>. The team is excited and everyone’s ready to launch. Then six months in, your budget has been blown, key features don’t work the way users need them to, and the project that was supposed to transform your business is now back down at the foot of the mountain.</p><p>But the problem isn’t bad design or poor code. It’s much simpler: you started building before you knew what to build.</p><p>Back in the early 2000s, we did the same thing. We’d come out of a client meeting and jump straight into design and development. We’d ask all the obvious questions, “who’s your target audience?”, “what does success look like?”, but we were only skimming the surface. We weren’t really digging into what their users actually needed. We had no idea what problems we needed to solve.</p><p>Our clients loved what we delivered. But a few months down the line, they began to realise what features their users actually wanted. And adding these in post-launch would cost them more money. The smiles turned to frustration. The excitement turned to firefighting.</p><p>It was time to take a step back and change our approach. Instead of jumping into design and build, we slowed down to understand. We asked tougher questions. We mapped out future needs. We analysed data. We did our research. We stopped treating <a href="https://sidigital.co/services/discover">discovery phases</a> as a nice-to-have and started treating it like an insurance our clients had to have.</p><p>Around <a href="https://www.mckinsey.com/capabilities/transformation/our-insights/common-pitfalls-in-transformations-a-conversation-with-jon-garcia" target="_blank" rel="noopener noreferrer">70% of digital products fail to hit their desired targets</a> according to research from McKinsey. Companies wasted tens of thousands of pounds designing and building features that their users simply didn’t want. And the cost of fixing those problems post-launch can be up to 100 times more expensive.</p><p>This isn’t about adding time to projects. It’s about not wasting the time you’ve already got. So let’s talk about why discovery phases aren’t just valuable. They are a must-have.</p>

We've seen it happen too many times

<p>Skipping discovery phases is an industry-wide problem, affecting projects big and small. And it’s leaving some interesting stories in its wake.</p><p>Remember Quibi? You’ve probably never heard of them. And that’s exactly the point. In 2020, former Disney Chairman Jeffrey Katzenberg and Meg Whitman, former HP CEO, launched a mobile-first streaming platform for premium short-form video. They had around $1.75 billion in funding, and an impressive list of A-List celebrities like Dwayne Johnson, Chrissy Teigen, and Steven Spielberg behind them to create the content.</p><p>But six months later, they shut down.</p><p>Quibi didn’t fail because of bad execution or poor timing. They failed because they didn’t validate that anyone wanted what they were building. They spent over $1 billion creating content before even asking their audience a single question. They assumed users would pay for paywalled videos when YouTube and TikTok were already delivering free, sharable content. By the time they realised their users wanted social features rather than premium isolation, they had already burned through nearly $2 billion.</p><p>Another example is Google Wave, an ambitious project launched back in 2009 that survived just over a year before being shut down. Why? Because Google didn’t figure out what users needed. Wave was billed as a groundbreaking new communication platform that would reimagine email by combining real-time collaboration, instant messaging, and document editing in one place.</p><p>But Google skipped the vital discovery project phase and brought a product to the market with no foundation to give users the answers to their problems and no clear value proposition. They made assumptions without validating them with users, which resulted in a product that users simply didn’t need. And, as it turns out, users don’t want a platform that merges all their communications into one place.</p><p>One last example is Panels, an app from YouTuber <a href="https://www.youtube.com/user/marquesbrownlee" target="_blank" rel="noopener noreferrer">Marques Brownlee</a>. The app was built on a simple idea – premium subscription phone wallpapers, and launched in September 2024. The app was born from comments on his videos, often pointing out how nice his wallpapers were.</p><p>Are comments on videos enough information to warrant building an app? No. In a world where background images are readily available for free on platforms like Unsplash and Pexels, it turns out nobody wanted to pay $50 a year for a subscription to get “premium” ones regularly.</p><p>Panels closed down in December 2025, and it ultimately boils down to skipping that key discovery phase. If the Panels team had conducted proper user research, they would have found out before even starting to write a line of code that there was simply no market for a premium subscription wallpaper app.</p>

An industry avalanche

<p>It’s easy to sit here and analyse failed digital product launches, but why does it keep happening? And to projects funded by big and small companies?</p><h3>Pressure to move quickly</h3><p>Key stakeholders are driven by results. They want to see tangible output from their investment. Discovery can feel like standing around when everyone wants to sprint. So teams often skip it and dive straight to design and build, only to discover six months in that they’re building the wrong thing. And what they end up missing is the key foundational information that underpins the entire project.</p><h3>Discovery gets mistaken for delay</h3><p>Nobody wants project delays. And stakeholders can be sensitive to this. They often see the research phase as a stalling tactic rather than essential groundwork. This is a dangerous misconception. Skipping discovery phases isn’t efficient; it’s a false economy that compounds into blown budgets and wasted time.</p><h3>Activity gets confused with progress</h3><p>Wireframes feel like progress. Code feels like progress. Research? That just feels like more meetings. Stakeholders confuse visible activity with actual value, ignoring the fact that building the wrong thing quickly is worse than building the right thing thoughtfully.</p><p>The result? Teams rush into execution, only to spend months, and tens of thousands, correcting avoidable mistakes.</p>

So why does this keep happening? 

<p>The most obvious cost of skipping a discovery phase is the failure of the project. But that’s not the case with most teams. There are more discreet, invisible costs involved. Most teams finish their project, but they finish with something that cost them twice as much, took significantly longer than it needed to, and doesn’t actually solve all their users’ problems.</p><p>These are the invisible costs. The ones that don't show up until you're deep in development. And by then, they've already compounded.</p><h3>Stakeholder misalignment</h3><p>Everyone thinks they're on the same page. They're usually not. The managing director has one vision, the project manager another, and the development team a different vision again. And these differences all stay hidden during the honeymoon phase of the project, the phase where everyone’s excited and inspired. But when real decisions need to be made, everything explodes. You’re three months in, the budget half spent, and stakeholders are arguing over features that should have been agreed on from day one.</p><p><a href="https://teamstage.io/project-management-statistics/" target="_blank" rel="noopener noreferrer">Research backs this</a>. Lack of senior management involvement in projects is the primary reason that 33% of projects fail. And 78% of project managers say they want stakeholders to be more involved and engaged. A clear sign that plenty of projects suffer from a lack of alignment.</p><h3>Technical surprises</h3><p>When you skip discovery phases, you fail to uncover the technical landmines until it’s too late. That seemingly easy integration you thought would be a quick win? It needs <a href="https://sidigital.co/faraday">bespoke middleware</a> to work. That feature the client requested? It doesn’t work with the platform architecture. These kinds of discoveries when a project is in full motion mean more than just delays; they force costly reworks and scope creep.</p><p>Fixing these kinds of issues during development phases can <a href="https://www.blackduck.com/blog/cost-to-fix-bugs-during-each-sdlc-phase.html" target="_blank" rel="noopener noreferrer">cost up to six times</a> more than catching them during a discovery phase. <a href="https://www.blackduck.com/blog/cost-to-fix-bugs-during-each-sdlc-phase.html" target="_blank" rel="noopener noreferrer">15 times more</a> during that testing phase. And post-launch? <a href="https://www.blackduck.com/blog/cost-to-fix-bugs-during-each-sdlc-phase.html">Up to 100 times the cost</a>.</p><h3>Unvalidated users need</h3><p>Around <a href="https://www.pendo.io/resources/the-2019-feature-adoption-report/" target="_blank" rel="noopener noreferrer">80% of software features are rarely or never used</a>. Why? Because teams build in functionality they assume the user wants based on internal logic and stakeholder preference, not actual user research. And this results in bloated products full of features that nobody asked for. As for the things users genuinely need, these get deprioritised or forgotten completely.</p><p>If you’re a startup, this can have detrimental effects on the business. Around 42% of startups fail because of “no market need”. It’s the number one cause of failures according to <a href="https://www.cbinsights.com/research/report/startup-failure-reasons-top/" target="_blank" rel="noopener noreferrer">CB Insights’ report</a>, which analyses nearly 4,000 failed startups. Teams assume, users needs aren’t met, and money gets wasted.</p><h3>Scope creep</h3><p>Requirements are often vague without a discovery phase. And vague requirements mean endless clarification needs during build. Every clarification then opens a door to a new idea, which in turn shifts priorities and even “while we’re at it” additions. Before you know it, your project has ballooned into a bloated mess that’s missed the deadline and blown the budget.</p><p><a href="https://www.pmi.org/learning/thought-leadership/pulse" target="_blank" rel="noopener noreferrer">Research from PMI suggests</a> that organisations can avoid budget loss and project failure by investing in communication and alignment work upfront, which is exactly what discovery phases provide.</p><h3>The real cost</h3><p>These issues each feed into one another. Misaligned stakeholders result in woolly requirements. Woolly requirements create scope creep. Scope creep leads to technical limitations. Technical limitations force rework. Rework burns through budget. Suddenly, your project is 45% over budget. <a href="https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/delivering-large-scale-it-projects-on-time-on-budget-and-on-value" target="_blank" rel="noopener noreferrer">Research from McKinsey</a> shows this to be the average budget overrun on large-scale digital projects.</p><p>While discovery phases don’t mitigate all the problems, they do help to surface them before they get expensive. And that’s the difference between a successful project and one that can barely make it across the finish line.</p>

The invisible cost

If you’re unsure if your agency is carrying out a thorough and full discovery phase, download our free checklist to see what your agency is (or isn’t) doing right. 

Download our free discovery checklist

<p>Agencies all work in different ways, ask different questions, and present their findings differently. So how do you know if yours is doing it properly? Let’s break it down:</p><h3>A proper workshop, not just a kick-off call</h3><p>A good <a href="https://sidigital.co/services/discover/workshops">discovery workshop</a> shouldn’t feel like a glorified briefing session. It’s where your agency digs into the detail, like your business goals, your users, your constraints, and any assumptions you have. By the end of it, they should understand your problem as well as you do. If they’re not asking uncomfortable questions, they’re simply not going deep enough.</p><h3>Research that goes beyond your brief</h3><p>Your agency should be doing the heavy lifting you have time for. That means <a href="https://sidigital.co/services/discover/research">market research, competitor analysis, and most importantly, user research</a>. This is where assumptions are validated or killed. If your agency is skipping straight ahead to a solution without speaking to real users, that’s a huge red flag.</p><h3>Analysis that rules things out</h3><p>Proper discovery doesn’t just generate ideas, it eliminates them, too. By the time your agency comes to present their findings, they should be able to confidently tell you what will and won’t work and why. If everything is still on the table, the analysis hasn’t been rigorous enough.</p><h3>Evidence-backed solutions</h3><p>Any <a href="https://sidigital.co/services/discover/solutions">proposed solutions</a> should be connected to and backed by the research. Every feature, design decision, and technical choice should have a valid reason behind it. If your agency can’t explain why something’s included, it probably shouldn’t be.</p><h3>Genuine alignment, not just sign-off</h3><p>Discovery works if everyone’s genuinely on the same page, not just nodding along. This is the time to discuss disagreements, clarify priorities, and make sure leadership, and stakeholders, project managers, and delivery teams share the same vision. Skipping this step is how you end up with arguments three months in.</p><h3>Measurable success metrics</h3><p>Success needs to be measurable. Not vague goals like “better user experience”, but real numbers. Conversion rates, task completion times, order values, support ticket reductions. If you can’t measure it, you can’t prove the project worked.</p><p>That's the theory. Here's what it looks like in practice.</p>

What good discovery looks like

<p>Let’s <a href="https://www.wightlink.co.uk/" target="_blank" rel="noopener noreferrer">look at Wightlink</a>, an award-winning ferry service connecting over 4.3 million passengers a year between the Isle of Wight and Hampshire.</p><p>Their website is enormous. It features complex booking functionality, multiple user types, time-sensitive travel decisions, and a user base with varied needs. From daily commuters to holidaymakers. A project of this scale can’t afford assumptions.</p><h3>So, we didn’t assume anything</h3><p>Before we even opened Figma or started writing a single line of code, we ran an in-depth <a href="https://sidigital.co/services/discover">discovery phase</a> with the team at Wightlink. We also ran <a href="https://sidigital.co/services/discover/workshops">workshops during actual ferry crossings</a> to understand how their customers interacted with the service. We asked what we thought were obvious questions: does this page layout work? Is the price displayed clearly? Are booking tools prominent enough? Turns out the answers weren’t so obvious after all.</p><h3>What we discovered was invaluable</h3><p>We discovered different user groups had very different needs. Daily commuters needed speed. Holidaymakers needed reassurance and detail. Staff needed CMS functionality that streamlined their workflow. None of this was insight we could have guessed. It came from asking and listening.</p><p>Our research directly informed both our <a href="https://sidigital.co/services/design/digital-design">UX decisions</a> and technical architecture. We validated every feature to ensure it was there for a reason, not because we thought it was needed. Every design decision connected back to real user insight and behaviour, not our own assumptions. The outcome is a website that actually serves users properly because we knew what their users needed before we started design and build.</p>

Discovering Wightlink

<p>It’s easy to say in hindsight, but we know if we’d skipped the discovery phase and gone straight into design, we would have built a website that wasn’t what users wanted or needed. And the project would have become another expensive statistic.</p><p>Instead, it’s a case study in what happens when you invest in discovery upfront.</p><p>You can read more about <a href="https://sidigital.co/work/wightlink">how we helped Wightlink</a>.</p>

<p>Ensuring discovery phases happen, and happen properly, can be a bit daunting. It’s often difficult to justify the expenditure, so here are some tips for getting it across the line:</p><h3>Pitching discovery to leadership</h3><p>Most projects run aground here. Key stakeholders and decision-makers see discovery phases as a delay, not an investment. To make it smoother:</p><ul class="list-bullet"><li value=1>Make sure you position the discovery phase as risk mitigation, not just research. Leadership tends to understand the value of insurance.</li><li value=2>Throw stats their way. Tell them fixing the problems post-launch could cost up to 100x more than catching them during discovery. And use case studies like Quibi and Panels to demonstrate the value of user research and insight.</li></ul><h3>When budgets are tight</h3><p>The luxury of a discovery phase isn’t an option for everyone, especially when it comes to project budgets. If you’re worried about budget:</p><ul class="list-bullet"><li value=1>Opt for a minimum viable discovery. This should cover a stakeholder alignment workshop and at least one round of user validation. This helps to reduce the risk when budgets don’t allow for a full-blown discovery phase.</li><li value=2>Prioritise the riskiest assumptions first. If you know you’re assuming key features, validate those before anything else. You can shut down unfounded ideas before they get too set in.</li><li value=3>Approach discovery proportionately. Cut your cloth to suit, and carry out a discovery phase that both fits your budget and your project needs.</li></ul><h3>Red flags to watch out for</h3><p>Keep an eye on any red flags as you work through the project. Self-diagnose as your project progresses if you start to see:</p><ul class="list-bullet"><li value=1>Disagreements between stakeholders relating to priorities three months in.</li><li value=2>Knee-jerk requests, and “while we’re at it” asks becoming constant.</li><li value=3>Unanticipated technical blockers, like platforms that don’t support what your users need.</li><li value=4>Features built on opinion rather than evidence.</li></ul><h3>Get outside help</h3><p>If you find your project going off the rails, it’s time to get external help. This is key when:</p><ul class="list-bullet"><li value=1>Internal teams are too close to the problem to be able to work out a solution.</li><li value=2>You need specialist skills and insight that you don’t have in-house.</li><li value=3>An external perspective on the problem can challenge assumptions that internal politics won’t allow.</li></ul>

Make it happen

<p>Settling into basecamp before starting the climb is key to a project’s success. Putting the time, effort, and investment into the discovery phase is insurance. You, your team, and your stakeholders can work through your project knowing you’re creating a product that’s going to meet your users’ needs, as well as the business’s own goals and KPIs.</p><p>Discovery isn’t a nice-to-have or a box-ticking exercise. It’s the difference between a project that gets stuck halfway up the mountain and a project that reaches the summit. So, before you get stuck into your next big build, take a step back. Make sure the groundwork has been done properly. No corner cutting, no holding back. And if you’re unsure whether your agency is carrying out a thorough discovery phase, download our free checklist to see what they are or aren't doing right.</p>

It’s time to change your mindset

Lead Designer

Sam Leonard-Rendell

<p>There’s a lot to organise and the pressure’s on to get things right. With all this to contend with, it’s important to accurately identify the key insights. This improves efficiency and provides value to your clients with clear feedback.</p><p>We have tried many different ways of recording feedback with participants. Each method became convoluted, making it harder to analyse data at the end of a test. So, we began looking for ways to improve our process.</p>

User tests can be full-on

<p>We have recently been looking at <a href="https://www.youtube.com/watch?v=8AKWYH1EzJI" target="_blank" rel="noopener noreferrer">Design Sprints and how user testing is compressed into one day</a>. This technique is simple in its approach and has been successful for us. It removes the bloat and keeps the work focussed. Today, we want to share and break down this way of working.</p>

Stay simple and don’t over complicate

<p>Before starting a user test, you will need:</p><ul class="list-bullet"><li value=1>Whiteboard / whiteboard wall</li><li value=2>Whiteboard markers</li><li value=3>Sharpies</li><li value=4>A pad of blue Post-its</li><li value=5>A pad of pink Post-its</li></ul><p>Now that you have your equipment, you can begin to record your user feedback. We usually test with 5 participants as this tends to be the sweet spot of not too many or too few. <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/" target="_blank" rel="noopener noreferrer">What Nielsen Norman Group wrote about testing with 5 users still holds true</a>. You can find up to 85% of usability issues with 5 participants. ‘Add more and more users, you learn less and less’.</p><p>Before the first person arrives, you will need to divide up your whiteboard. Using a whiteboard marker, split the board into 5 columns. Add the names of your participants across the top. Down the left-hand side, add rows and label each according to the task or page you are looking to test.</p>

Preparing for user testing feedback

Sign up for all the latest news and updates from Si digital.

Get the latest news and updates

<p>As you do your user tests, it is important to make quick notes as you go. We tend to analyse our user tests in pairs to prevent any misinterpretation of comments. This is where we use our post-its to record different types of feedback. However, make quick, rough notes before transferring them to post-its at the end. We use blue post-its for positive comments and pink post-its for negative. A negative comment could mean a participant struggles or has to think about what to do next. Or they might communicate their problem out loud. Write these down as they are super important.</p><p>Once you have your feedback, stick the post-its into the relevant row for that participant. As you do this, discuss and compare the feedback received and see where there is overlap. </p>

Recording user testing feedback

<p>Repeat this process for each of your user testing participants. Making notes as you go, then writing down the feedback on the relevant post-its at the end of each test. Once you have all five up on the board, you’re ready to begin looking for patterns. They should really jump out at you!</p><p>If you take a step back from the board, it should become quite clear where the problem areas are. Look closer and you should be able to group specific insights. This will help you to build a picture of where the most common issues are.</p>

Repeat for each user test

<p>This is a simple and quick technique to record user testing feedback that a group of you can do together. It helps improve collaboration and the process of gathering insights.</p>

That’s it

Have a read of some of our other articles

A simple way to record your user testing feedback

<p>In an ever-changing digital world, the last thing you want to do is stand still if you're looking to stand out. Your website might be the first impression for visitors to learn about what it is your business does and we know how much weight negative experiences hold, whether it's an accurate representation of your services or not. That's why making UX and UI improvements to refine your website, rather than simply launching it and moving on, is an invaluable practice.</p><p>Take the opportunity to show users that you care about their experience as much as you care about presenting yourself in the best light. A killer way to do that is through iterative design.</p>

<p>It might seem counterintuitive, but there's a crucial difference between improving your website and fixing it: the latter meaning you’re making it better without it first being broken. You're ahead of your game rather than trying to catch up. In other words, you're in control of what you're changing, why you're changing it, and how you're going to do it – and that is an exciting place to be.</p><p>With digital environments constantly shifting, adaption shouldn't be a knee-jerk reaction. Using iterative UX and UI improvements, it becomes a steady evolution over time based on user testing, feedback and research from platforms like Hotjar, Google Analytics and Microsoft Clarity. This means that you're not just addressing changes as and when your business grows, but focusing heavily on what users want most from your site and responding to it in good time.</p><p>Our work with Wightlink is a fantastic example of how iteratively updating websites based on user feedback improves performance and overall experience for visitors in the same breath. First, we successfully redesigned a user-centric website built around how ferry passengers actually plan and travel. Where holidaymakers look for reassurance and clarity, regular commuters need speed and efficiency, so it was important to consider the individual requirements from each group as well.</p>

Improve, don't fix

<p>Then, by working closely with Wightlink, we uncovered persisting pain points and the solutions needed to fix them, resulting in the addition of Best Fare Finder and Wightlink Explorer post-launch. <a href="https://sidigital.co/work/wightlink">Read the full case study here to learn how our research shaped three core design principles that made all the difference</a>.</p>

<p>On top of overall user experience, iteratively updating your website means you can also make processes more efficient. When we rebuilt leading connector company Harwin's website from the ground up, we brought together their Salesforce system for product data with Bynder for digital assets, supported by a Payload CMS for content management, all through our secure <a href="https://sidigital.co/faraday">Faraday middleware</a>. It's not only made operations smoother, but more adaptable too. For example, switching out different tools based on changing business needs, and automatic syncing of new products to ensure everything is always up to date on the site.</p><p>We also continue to launch new updates as and when they're needed for Harwin, including the helpful Cable Configurator – a user-focused experience for specifying bespoke products for customers’ projects. Plus, by using Microsoft Clarity session recordings, we've made significant UX improvements to a whole host of features, such as a clearer navigation bar, better drop-down menus, improved type hierarchy, a more user-friendly contact page, a clearer layout for complex data on product pages, and plenty more.</p><p><a href="https://sidigital.co/work/harwin">And see how we slashed website load times by 90% for Harwin here</a>.</p>

A streamlined evolution

<p>Cohesion is key when it comes to having a recognisable business. As it grows, it's inevitable that your brand look and feel might change with it, so clear alignment is crucial to instill both trust and confidence in your customers. Plus, by updating iteratively in-step with competitors' sites and user feedback, it doesn’t have to be a huge overhaul – small changes are just as effective as the big ones.</p><p>We mentioned at the start of this article that the last thing you should do is stand still as the digital world continues to move forward – that applies to us as well. Besides regularly improving our own site, we have a proactive approach when it comes to our clients' needs. Rather than waiting for them to discover a pain point or issue that needs addressing, we're already thinking about what solutions would work best for them next.</p><p>As long-term partners, our clients know we have their interests in mind and trust that we'll bring something to the table that doesn't just solve a problem, it's already part of a larger iterative approach strategised to improve their product.</p>

Always looking ahead

Totally free, no strings attached, we promise.

Download our UX & UI Self-Assessment 

<p>Looking for someone to help tackle your problems with creative solutions? <a href="https://sidigital.co/contact">Drop us a line. We're always keen to chat.</a></p>

Why UX and UI iteration are crucial practices for stand-out websites and apps

Let's stop pretending we can skip project discovery phases

<p>Back in 2019, we created something that resonated with designers everywhere: a series of posters bringing Jakob Nielsen's usability heuristics to life. These principles, <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">originally outlined in his 1994 article for The Nielsen Norman Group</a>, struck a chord with so many people that we've given them a fresh look and a new lease of life.</p><p>Here's the thing about usability heuristics, they're not rigid rules you have to follow to the letter. Think of them more as guiding principles that form the bedrock of solid usability practices. We've leaned on these time and again <a href="https://sidigital.co/services/design/digital-design">when designing interfaces</a> or digging into usability test results. They give us a clear framework to work within and align our thinking.</p>

Download our 10 Usability Heuristics Posters

<p>Here at the Si digital studio, we wanted our walls to reflect the work we do, so Jakob Nielsen's original article got us thinking, why not turn these "10 Usability Heuristics" into something visual and inspiring?</p><p>Fast forward to today, and these posters are printed, framed, and hanging in our studio. They've become such a <a href="https://sidigital.co/services/design/digital-design">valuable part of our daily work</a> that we wanted to share them in their new form with the wider design community.</p><p>This Lab Note showcases a couple of our 10 posters, and we're making them available as free downloads in PDF, PNG, and JPG formats. We hope they inspire your work as much as they've inspired ours. Feel free to share them with your team.</p>

Bringing heuristics to life in our studio

The 10 Usability Heuristics – updated for 2026

Starting March off right with a few doughnuts for the team 🍩

<p>Starting March off right with a few doughnuts for the team 🍩</p>

Welcoming in March

Another busy month here at Si HQ. Here’s a quick look back at what February had in store for us.

<p>Another busy month here at Si HQ. Here’s a quick look back at what February had in store for us.</p>

February Wrapped 📸 

We’ve already raided these ahead of Easter…

<p>We’ve already raided these ahead of Easter…</p>

It’s not too early for a Creme Egg, right?

We’re back in the swing of things after Christmas and New Year. Check out what we’ve been up to this month 🎞️

<p>We’re back in the swing of things after Christmas and New Year. Check out what we’ve been up to this month 🎞️</p>

January Wrapped 📸

We’ve been tidying up the office the last couple of weeks and found a few retro devices in the cupboards. A total throwback for a lot of us. We used to test on these devices back in the day!

<p>We’ve been tidying up the office the last couple of weeks and found a few retro devices in the cupboards. A total throwback for a lot of us. We used to test on these devices back in the day!</p>

We woke up in the 00’s today 📞 

We were at Shaping Portsmouth 2026 on Friday, listening to some genuinely inspiring people talk about the future of our city. Plus, Steve got his moment in the spotlight 🎤

<p>We were at Shaping Portsmouth 2026 on Friday, listening to some genuinely inspiring people talk about the future of our city. Plus, Steve got his moment in the spotlight 🎤</p>

Conference day ✨

Love it when surprise biscuits show up at the office 🍪

There's something satisfying about cracking open fresh colour swatches for a brand project. These new guides are helping us lock down the perfect palette for a client who's going through a complete rebrand. The best part of a brand job? Getting to build brands from the ground up.

<p>There's something satisfying about cracking open fresh colour swatches for a brand project. These new guides are helping us lock down the perfect palette for a client who's going through a complete rebrand. The best part of a brand job? Getting to build brands from the ground up.</p>

Fresh Pantone guides just landed on the desk 🎨

It’s nearly Christmas, and as we shut down for the festivities, we thought we’d share some of our favourite moments from 2025. Have a merry Christmas and a happy New Year! See you all in 2026 🎉

<p>It’s nearly Christmas, and as we shut down for the festivities, we thought we’d share some of our favourite moments from 2025. Have a merry Christmas and a happy New Year! See you all in 2026 🎉</p>

December Wrap-Up 📸 

It’s been a busy one with projects kicking off, conferences, and so much more…

<p>It’s been a busy one with projects kicking off, conferences, and so much more…</p>

About

The digital agency for brands that demand more

Working with us

A long-term partner

We tackle challenges together

Quality builds, every time

Clear communication

Our culture

Behind the Scenes

From the studio