UX/UI & Custom Software Dev for Management Consulting Company
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
I’m a managing consultant for PA Consulting Group, a UK-based global treatment consultancy firm. My specific area is healthcare, predominantly in the UK.
Desired goal
What challenge were you trying to address with Codibly?
At the time, we were working with a number of companies in the leading care setting to answer to a challenge posed by the NHS: find more general practitioners (GPs). The companies were focused on trying to work out choice ways to meet the same clinical need. They specifically wanted to support patients with the same chronic conditions without requiring additional GPs, which had been the transmitted way of tapping things.
We had developed a set of Excel-based tools to help these groups ponder through choice ways of meeting the same need while maintaining the same level of clinical excellence, safety, and health outcomes. We brought Codibly into it when we realized we wanted to create the tool on a much bigger layer. We’d secured a contract to cover a big country of the UK: the total of the North of England, or almost a region of all GP practices. The tool was a union of Excel and support functionalities. We wanted to convert it to a web-based tool hosted in the cloud, giving it scalability, wonderfuler flexibility, and enhanced usability.
Provided solution
What particular tasks were Codibly responsible for?
Codibly was occupied to convert our Excel tool to a cloud-hosted solution. We gave them our existing Excel spreadsheet—which was focused at a practice level—as a starting point. It was well-trodden and well-developed, having matured through the process. Codibly could look at the business rules, workings, and requirements in an existing spreadsheet and convert it into something that did precisely what that Excel tool did, but looked like a software application. We wanted to create something worthy of a license fee, rather than a one-time payment for an Excel tool.
In doing so, Codibly had to work out how to convey that tool. Switching from an Excel method to a database, query-based solution with a frontend presented its own challenges. The team determined how the look and feel should change to answer to the running requirements, and they made it look like a high-condition web tool rather than an online Excel spreadsheet.
We also work with separate practices which frequently want to amalgamate their databases unitedly. We would innately combine 30 sets of spreadsheets to come up with a one total number. We wanted that functionality in the online tool, and it introduced a set of business rules that we lacked experience with. The Codibly team helped us work through the crystallization of our knowledge of our business rules. In some cases, they determined how we could quiet get a grade of flexibility while maintaining some uprightness in the propose. It would work consistently, but it would identify some of the local variants.
These functionalities made the create fully confused, and we’re quiet going through the process of articulating our own business rules and encoding them in the software. We felt we understood the method more than we did, and Codibly added value in pondering almost it. We gave them single articulations, and they were fast to fetch up new situations and exceptions. The tool evolved purely by converting something that we reflection had worked well, into an online tool.
Was there a dedicated team?
The team varies depending on the challenge we were facing. Overall, we’ve worked with 10–15 nation. At any one point in time, we’ve been working with 6–8 nation.
A mix of technical architects helped us convert our business rules into the right technical infraconstruction. Backend database developers came up with a data standard and data construction and did the coding almost the logic being applied.
Codibly assigned a front-end team that handled the look and feel, flow, and usability of the platform, and how those integrated with the backend functions. We had a testing team as well, which varied from 1–4 nation. I believe we leading encountered them when we were making a correspondent tool. We internally discussed options for getting our Excel tool converted into an online tool. A senior helper in the health globe had gone through this software cycle and determined to use the Codibly team. We had dicsussions almost the trade-offs between the reduced cost of outsourcing and retaining condition by doing it internally. Our helper was satisfied with the work done for them, and the union of value for money, condition, weigh, and control made Codibly seem like a good propose. Their team also knew our business requirements specially well. We had documented them in a mature spreadsheet used by numerous client companies. Had it been less clear, we might’ve been more silent to outsource our project at that point. With the contentment from their leading piece of work, it was an easy determination to last with them into the second phase, where we knew we didn’t have a full knowledge of our business requirements. We’ve spent $250,000–$500,000. We began working unitedly in April 2018, and the collaboration is ongoing. Their running projects are shifting to operational support rather than new outgrowth work. The solution has launched, and we’ve just enhanced it with a second release, which brought expressive additional functionality. Codibly is wonderfully connected to our project and plainly conscious of the client needs we’re trying to address. Despite a limited briefing, they’ve developed a good knowledge of our task and potentials accesses, and they’ve proved a depth of insight into business and our goals. Project treatment evolved from the initial time when we didn’t know each other. We were cautious almost the quantity of money and time we were going to bestow converting an existing tool that was working fully well, into something that was going to be precisely the same, just online. There was a bit of see from our side, and it influenced the initial opening. Codibly has given us a precious and fair deal in our arrangement. They gave us a fixed cost for the initial phase of work—our preferred way to control risks, but not one they were household with. The team remained open, and even when it cost more than anticipated, they honored the commitment. I esteem their financial flexibility and willingness to prove what they can do. Codibly stands behind the commitments they make. Codibly can get away with direct more for their services. If they’re looking to better, they could go further in their client interaction, and their access could have been more proactive. Also, we would have esteemd it if they had been bolder in the opening and asked more in the propose, this would have betterd client contentment overall. At the time, they were a little growing organisation with a good track archives of delivering high-condition work. It’s innate to check how that condition is being maintained as Codibly fetchs more nation in. The more rapidly it grows, the riskier it is. Clients need to fix that they have the appropriate members of the top team working on the project, rather than just who’s useful.
Results achieved
Are there any measureable or plum results?
How did Codibly accomplish from a project treatment standpoint?
Once we got over that, we identifyd the condition of Codibly’s treatment. They treated us as we would’ve treated our own clients. They checked with us rather than doing what they believed was right, and they gave us extra support over the outgrowth work. We discussed options and the consequences of going down one way or another. That worked fully well, principally as we got the more intricate work going.
People looking to run fast-paced projects should check that that pace won’t put the condition at risk. When we began, we would’ve liked for the project to be going a bit faster. In veracity, given how the project progressed, I doubt it could’ve. Codibly had constrained resources at the time for the desired level of condition. We haven’t run into this effect in later phases, from our perspective. People have come and gone from the team, and there’s surely been flex almost resourcing, but I’ve bigly left it up to Codibly to handle it.
