Why work in our Digital Enablement capability?
At Sysdoc, we understand that Digital Enablement is not just a matter of technology, but how we mere humans interact with that technology; it could be the best system in the world, but if nobody can use it then it might as well be a very expensive doorstop.
Working as part of the Digital Enablement team you will be working with other multi-skilled individuals putting your technical skills to the test developing creative solutions to varied and complex problem statements with human-centered design as a core pillar for everything we do. We are collaborative and supportive of each other, blending our skills to ensure you are always playing to your strengths whilst also giving you the opportunity to expand your skillset. Our customers are often ambitious but unaware of how they can do technology better, we try to promote innovation through edge technologies (where sensible) and take a pragmatic, common-sense approach. Autonomy and creativity is encouraged, and we take the view that everyone has a voice; if you’ve got a better idea on how we should do something, we’ll run with it.
You will work with a range of web-based frontend technologies, platforms as a service and bespoke backend solutions where we feel we need to augment an existing system or technology to get a better result for our clients. We blend technology, user experience and the (world famous) Sysdoc DNA into everything we do giving you a much broader workplace experience than simply writing code; understanding why we are writing code is just as important as the code itself, what are we trying to solve and why.
You will work within SCRUM or Kanban methodologies (depending on the size of the project) where we regularly review how we are performing, how we can perform better and celebrating our successes. Our projects are typically a mix of innovative user interface, intelligent information design and future & upgrade focused application design – we want our solutions to be able to evolve and improve without racking up technical debt over time.
Testing and quality assurance play a key part of working in the team through paired programming, peer reviews and effective testing strategies. We never underestimate users and take a defensive approach to solution implementation ensuring that the user always gets some feedback and knows what to do next if something goes wrong.
We are a social and close-knit team (as is the wider Sysdoc team) and have regular get togethers (albeit virtually now) to have a beer, chat and catch up on recent events or other cool stuff going on in the tech and wider world.
Latest blog postsSee all blog posts
Sage article: Cloud adoption, why you should work on supporting your employees first
Manufacturers can save time, effort and money through cloud adoption projects. Around one third of UK manufacturers purchased cloud computing services in 2020. Most would have done so to make the most of well-known benefits such as improved productivity, accessibility, reporting and data security, as well as lower operating and IT costs. However, if you’re looking at cloud adoption for your manufacturing firm, it’s really important that your people are a key part of the process. Rather than implementing the changes then informing your employees, they should be involved from the start. Read this article to find out why your employees should play a role during every step of your cloud journey, how to support them, and how to avoid potential pitfalls within your team. After all, you don’t want to get this wrong and pay a hefty price for delays or even lose key people.
Lessons from Consortium working
An introduction to my experience At the beginning of this year, I started a new project working with a new client and taking on a new role for a large transformation programme. I have worked alongside other consultancies on previous programmes in the past, but this was a first for me, working within a partnership from the offset.
Why Process Excellence is key for a successful ERP Implementation
I have been reflecting on my experiences working on ERP implementation/upgrade programmes whilst also listening and hearing to what others have to say. I think back to these projects and notice everyone was working hectically towards the programme ‘Go – Live’ and were under the impression that once they achieved this Go - Live then we have successfully implemented a new ERP System and our job is complete. I think many people can agree with me that a Go – Live date is just the start of the journey. We have got to think about the people, culture, education, efficiency in processes and where can we reduce ‘waste’.