We strive for providing a user-centred design. This means creating a tailor-made system by determining who the users are, their experience levels, their objectives and tasks as well as what functionalities they want from the system. The needs analysis focusses on these specifications to guide us in creating specific requirements in the desired system. The importance of the needs analysis is to identify and understand the flow of information within an organisation.
The research we conduct during a needs analysis concentrates on covering the most important issues that can be addressed by the new system. This can be done through carrying out stakeholder or staff interviews, surveys or focus groups. We pay special attention to how research is conducted. Using the right techniques to acquire information and asking the right questions not only makes easier for the users to give the answers we’re looking for but also clearly indicates how we can meet their needs.
The implementation of a large system is met with lots of resistance, it’s therefore essential that proper change management is done. The process is threefold: we start preparing for change by identifying points of resistance; managing change and finally reinforcing it.
Our use of the Kanban method in Project Management addresses the human tendency to resist change while ensuring a smooth and streamlined workflow during change management. Kanban helps us acknowledge the resistance to change by ensuring current practices are understood as they are practiced. We pursue improvement through evolutionary change and encourage acts of leadership at every level. We create incentives for people to participate and promote the system by making them feel part of it. All big development projects are broken up into phases that are handled individually to reduce the risk of miscommunication.
The final phase, project management, involves the planning, executing and closing of the project. Firstly, we determine the scope of the project. The scope includes the goals and objectives, tasks to be carried out, resources available, costs etc. Without it, the project has no direction and the chances of success are reduced. Multiple people and developers are involved in the development of a new system, they must be organised to maintain the scope of the project. We ensure we’ve established a key contact available to the team to provide clarity or alert crises. Establishing a communication path that is clear and seamless has several advantages for the team, a few of which include efficiency, accuracy and reaching goals timeously. Having a mutual channel for communication is a good way to collaborate. This way a shared meaning is established, expectations are managed and we can ensure collaborating will work for both parties.
Next we formulate a project plan to illustrate how to go about achieving the objectives of the project. It creates expectations and ensures they are managed properly. We refrain from taking a one-size-fits-all approach to the models applied to projects; this may have limitations because businesses tend to differ. The models we use cater to your specific needs as determined by the needs analysis.
Our experienced team will guide your organisation through the adoption of your new SharePoint Intranet. Training includes both onsite training and training material such manuals or eLearning material.
The majority of Intranets fail because they’re planned badly or because they’re implemented badly. Don’t fall victim to these pitfalls - contact us to find out how we can help you develop and implement your company SharePoint Intranet.
Have a look at our portfolio.