Blog

We catch up with Nasima Alam, who after taking a career break in IT to look after her young family, joined Infomentum as a Test Analyst. We find out about her onboarding experience at Infomentum and how she balances her role as a working mum in Tech.

Red Nose day sees Infomentum raises £400 for Comic Relief - with a few red noses, some good (and bad) jokes and the Fantastic Five taking a pie in the face!

Keeping the ball rolling on I>M Wellness over the festive season... 

The run up to Christmas is arguably the best time to come together to celebrate our shared experiences with Wellness this year. 

On October 10th, we celebrate World Mental Health Day. At Infomentum we've recently made a pledge to change how we think and act about mental health, and we've decided to dive right in and really get involved. Let's begin with some background about mental health at work. We'll discuss a topic that a lot of people might not know much about, and focus on our initiatives to get us all talking about, understanding, and looking at mental health in a different way. 

In the second installment of our 'A Day in the Life of...' blog series, we catch up with David Weston, Head of QA at Infomentum, to find out what his typical day looks like. 

We are celebrating a decade in business!

Infomentum has celebrated its 10th anniversary. Starting life as technology implementation experts in Oracle WebCenter portfolio, the business has experienced rapid growth over the years which has seen its capabilities expand.

Now in its tenth year, we offer our customers a wide range of services; from digital acceleration consulting, to technology implementation in the areas of content and process, data and analytics and customer experience, to full managed services and hosting. The business now offers expertise in best-of-breed technologies from Oracle, Mulesoft, Amazon, Adobe and more.

Kicking off our new blog series, ‘A Day in the Life of…’ our summer interns, computer science students Pratik Jadhav and Hasan Rafiq, reveal a behind-the-scenes glimpse of an intern’s typical day.

I chose to study computer science because…

Pratik: My dad is in the IT business so it’s something I’ve been interested in from a young age. I love technology and I wanted to understand how everything works, and how to develop everything.

Hasan: Other members of my family are in IT so I always knew about it. At first, I was going to go into dentistry, but I tried it out and I couldn’t see myself looking into other people’s mouths for the rest of my life! So I knew then that I wanted to go into computer science.

Wait: you need to read part 1 and part 2 first!

The fun side of cultural change

You’ll remember that last week I discussed the crucial need for a cultural change in how we dealt with time logging. After the CX team’s thorough research, we were ready to take the findings – and our ideas – to our board of directors. 

Hint: you'll need to read part 1 first for this post to make sense.

Phase 2: Imagine

The CX team got together to discuss the problems and carry out an internal ideation workshop to tackle them. We knew that we had 3 key tasks:

• Improve people’s knowledge of why time logging is important
• Create a culture of time logging as a habit; and
• Make the systems they needed to use simpler and clearer while having less of them!

It had been coming for a long time…

At the end of every month, developers scrambled to complete their timesheets, while the operations team were breathing down their necks, threatening them with sticks to get it done - and done right. The developers were left wondering why operations wanted their time logs so desperately. Surely they already knew what they had been working on? The operations team were scratching their heads as to why the developers didn’t do it; they had been reminded at the end of every month like clockwork, yet every month the same story. It was hugely frustrating for both sides, and was approaching boiling point. As soon as the Customer Experience team had a break between projects, we knew this was a top internal issue that had to be solved.