Ideas vs. Technology

> Ideas can be driven by a new technology
> Ideas often come from a “community” within the company
> Ideas require a higher level of research and development
- What does it mean? Who does it affect us? How will it work?
> Ideas can create more change within a company than a technology
- Affects multiple levels within an organization
- Requires deeper participation with employee population

> A technology can be selected to fulfill an idea
> A technology recommendation can come from anyone within an organization
> A technology requires a lower level of research and implementation
> A technology can usually only affect a single group within the employee population
- Project Managers
- Developers
- etc.

Selecting the Right Idea

> Concept Screening
- Comparing options against a baseline benchmark.
- Compare against factors like cost, reliability, time etc.
> Delphi Method
- Explore ideas or gain consensus with remote group.
> Force-field Analysis
- Exploring forces for and against an idea (pros and cons).
> The Hundred Dollar Test
- How will you spend $100 on your ideas?
- Select the idea that best matches your budget.
> The Kipling method (5W1H)
- Ask simple questions for great answers.
> Negative Selection
- Sort out the ‘definitely nots’ first.
- Must Haves, Maybes, Can Live Without etc.
> NUF Test
- Score idea based on how New, Useful and Feasible it is.
> Pause
- Reflect for a minute before deciding.
> PINC Filter
- Evaluate Positives, Negatives, Intriguing and Concerning elements.
> Six Thinking Hats
- Look at ideas from different viewpoints.
- Information, Judgment, Creativity, Intuition, Optimism, Thinking.
> Swap sort
- Sorting a short list by priority swapping.
> Voting
- Democratic casting of votes for the best idea.

Selecting the Right Technology

> Assemble a selection group composed of people from every part of the organization who will use the software, including key decision makers.
> Come to an agreement about the business processes that will be automated before looking at software. What are you trying to solve and/or improve?
> Factor in your company’s culture.
- If people are used to the freedom of choosing their work and working conditions, be careful not to choose a system that will destroy what people value most about their current business processes.
> Decide if you want an end-to-end, all-in-one package or one that integrates with current systems.
- Usually the latter are simpler and more cost-effective to implement – adheres to the “organic nature” of a company.
> Match the technology to your company size and the industry you’re in.
- Some solutions are better for small companies, some are designed for health-care enterprises and others for government services.
> Decide on your platform of choice.
- Will it be a thin-client Web-based one?
- Will it be a more traditional client/server model?
- Will it be an open-source or licensed solution?
> Don’t underestimate how long it will take to implement the package!

Preparation for the Presentation

Before presenting an idea or technology to management, prepare answers to the following questions:

> Where is the value?
- How will this idea/technology affect change in the company, and how will that change deliver value to your company?
- What are the $, resource and time costs to implement and support?
- What are the $ and time benefits after implementation?
> What will this idea/technology solve and/or improve?
- This should be a definite list of areas that will have a positive impact from the start.
- Long-term benefits should be categorized separately so there is strong awareness on short and long-term gains.
> Is there a strong “buy-in” within your company?
- The greater our community supports the implementation of an idea/technology, the higher level of success can be attained.

> Your Official Proposal
- Executive Summary
- Management, Key Personnel and Business Partners Involved
- Description of Idea/Technology
- Implementation Plan
- Management Plan
- Financial Evidence and Projections
- Supporting Documents

Gathering Feedback

After your official proposal is submitted, gathering feedback is critical to help re-enforce and/or improve the idea/technology being recommended.

> Specific areas requiring feedback:
- Quality of proposal
- Overall score on the idea/technology
- Areas requiring improvement
- Recommendations on improving the budget, timeline and resources for the implementation and support of the idea/technology
- What alternatives can be recommended
- Has it been done before at your company, and if so why did it not succeed
- What external resources have done in the past (ask friends, relatives, prior coworkers etc.)