Our experience has led us to some fundamental assumptions and guidelines:
* Technological change is constant and ever more rapid - so you can never rest in understanding the impact of change on your clients or your organization.
* Technological change is constant and ever more rapid. It is therefore essential that any system or service design not only accommodates regular change, but also facilitate it. We have found rapid prototyping, frequent testing, and regular user feedback keep the cost of change low and consistently add more value and result in more satisfied clients/users. While traditional business and action plans relate to a strategic framework, today's rate of technological change is too fast for a five-year framework. A more viable approach is- try it, test it, change it - over no more than a three-year cycle.
* Integration is a key framing parameter in any system/service design and implementation. Whether it concerns documents, multimedia assets, or applications, the ability to integrate is an essential concern and should inform all parts of the design, development and implementation process. In our experience, this usually necessitates cooperative work between IT staff and staff with domain expertise. Each must understand the consequences of design choices on information creation, management and distribution in a networked environment and be able to intelligently weigh the trade-offs involved. Integration as a design parameter also usually necessitates a major change in the information management culture of an organization, most especially as individual units create, manage and distribute the data they produce.
* Knowledge management is the ultimate goal of most our clients' systems and service designs. KM theory aside, to our clients, knowledge management means getting the right information to the right person when they need it to make decisions. Long-term goals include the ability to machine-process "smart tagged data" to provide new knowledge. NLI supports these goals, but until a full set of software and standards are practical for a complete implementation, we encourage our clients to design approaches that include ways to provide semantic meaning to data and that leverage the availability of the Web, Internet protocols and platform neutrality.
* Opportunity cost needs to be considered in its full perspective. To us, this means analyzing and designing models of information services that consider the cost of integration, update, maintenance, etc. We've seen firsthand the problems inherent when IT departments impose systems solutions without proper communication with impacted staff. But we have also seen the equally serious problems that occur when individual departments create information management systems that do not include consideration of vital IT issues. Our experience shows us it's essential for IT personnel to work closely with departmental staff to develop viable information solutions.
* Students, faculty, and other staff members are adopting, applying, and innovating in their use of rapidly changing technologies -so you have to see where they are and where your current services and programs fit.
* Your organization can never be all things to all people - but you can settle on a number of customized service models (different combinations of infrastructure investments) that are highly value-added.
* When your organization is indispensable to your primary clientele you will have succeeded - so your challenge is to find the right mix of organizational costs and the "value" that you add to clients as seen through their eyes.
* No change is without risk - but you can assess the risk and make your decisions about new directions accordingly.
* The University's technological investments (hardware, software, control mechanisms, people, skills, and support) are vastly important to university sustainability and must be leveraged (the most outcomes possible for the investment.) - You must understand your technological infrastructure in an environment broader than just your unit and just your university.
* Environments and contexts are changing as a result of changes in technologies and how people use them, so you cannot assume you know what those changes are. You have to talk to your clientele regularly. You have to build ongoing relationships with your known clients and those who might benefit from the new models of service you're developing.
As these assumptions and others like them hold over time, the organizations that succeed will be led by staff members who are listeners, learners, and decision-makers in the broadest contexts possible. Our Northern Lights Inc. tools provide new (yet structured) processes for staff members to develop and apply new skills that bring flexibility and continual learning.
In our coaching we do not tell people what to do. Rather we teach and train with methodologies that work over time and across environments.
Within the context of these assumptions, we always ask clients not to assume that their organization's future will be like its past - i.e., do not assume environment. We provide a Technology Landscape Report to understand and consider possible new conceptual models.
Our final assumption is that the only viable beginning point is the client, how they work, and what their behaviors are. Our tools are for staff members who want their organizations to be client-centered, value-added, and cost effective.
Recent Comments