WebOnyx Company Blog

Dynamic Development

Archive for January, 2010

IT and Development of New Products

Tuesday, January 26th, 2010

There is a great article over at Info World written by Bob Lewis that basically is trying to overturn the conventional wisdom of how to run an IT department, especially in larger companies. In a nut shell running the IT department “as a business, selling to its internal customers, its principal product is software that meets requirements” can become a train wreck. Running the IT department as a business causes the department to react instead of innovating, play catch up instead of leading the charge for new processes, and overall creates a system where IT and the business will be at logger heads, to the detriment of all.

“IT’s job is to recommend better ways to operate, using technical capabilities business managers might not even know are possible.”

Why are internal IT projects always behind the times? Because these projects are usually spearheaded by non IT individuals who do not live in the realm of the ever changing landscape of information technology. Instead IT should be integrated with the business and work every day to say how can we make this company run better!

“The job isn’t done when the software satisfies requirements. It’s done when the business runs differently and better”

So often IT projects are created to fit into already existing job processes, when in reality a new process should be created by the technology that works better for the company and it’s employees.

Anyways a great read for anyone who runs an internal IT department.

Social Knowledge Management

Friday, January 15th, 2010

One of our proudest accomplishments here at WebOnyx is the creation of SIX. What we bill as a social knowledge management system that helps organize people and content by interest and need. This is a quick video of what SIX does and what the philosophical underpinnings are in it’s development.

Choosing a Web Application Development Company Part 2

Wednesday, January 13th, 2010

A quick google search returns approximately 100,000 results for “web application development”, not even counting the adwords on the side. In the Seattle area alone there is a dizzying array of companies who offer their development services. There are some who promise you everything under the sun, and others who you are not sure exactly what it is that they do. Some specialize in ASP.NET development while others are more focused on PHP and mysql implementations.

So how does one evaluate a web application development company?

Simple. You have to ask, see what they have done in the past, and make sure their proposal meets the key ideals of what you want to accomplish.

Web application development is a difficult process so you must find a company that understands you and your idea. Software development is a complex process with many variables and unknowns that will crop up during development. The Internet is ripe with stories of great ideas for a software program that have gone uncompleted because of the complexity that can invade an idea. Even the best laid plans can be sidetracked by feature creep, bad developers and unfocused energy.

When evaluating a web application development company you must find out what their process is. What is it that keeps them from going off target and over budget? Does the company have good communication skills? Do they have a process in place to keep you informed of the progress being made? Do they do research and provide you with an explanation for exactly how they think the end user is going to use the product? And do they help you flesh out your idea with the knowledge that they have attained through past projects?

Having gone through many bid processes with our clients over the years it is always interesting to see what other companies present in their project plan. Quoted prices are usually all over the place and promises can be sky high. But in our experience projects are best presented in three phases.

  1. Creation of a prototype with, minimal features, but what are usually the most important features
  2. Fleshing out of the prototype with ideas that that did not make the first round of cuts, but add significant value to the product
  3. Final product features are implemented and some kind of support contract is agreed upon

The reason that you should look for proposals, and companies that work this way is because it helps avoid project failure, and it minimizes costs. If after a short period you believe that the company you hired is not worth working with it is easier to walk away from projects that are created with through this process then with a company who builds everything at once. With each step you get to see what is being created, and if the company can present functionality of a product in a fast and efficient manner.

Choosing the right company is essential for the success of your product, or idea. So choose wisely, or of course you could always just choose WebOnyx (:-

Developing Custom Web Applications Part 1

Monday, January 11th, 2010

Here at WebOnyx we tend to focus exclusively on innovative custom web applications that provide a competitive advantage to a company. Whether it is a knowledge management system for a fortune 100 company (whatissix), or a entrepreneurial consumer facing web application that takes messaging and instant notification of local events to a whole new level (knowberry). While we are not above taking a Joomla job, or making the occasional brochure site for customers, our projects usually take a month or two of development (or longer), and require some serious thought into how the user is going to interact with the product. The next couple of posts here at WebOnyx are going to focus on what it takes to create a successful web application and what the process should look like from start to finish for those who are interested in working with outside companies to create custom web applications.

There are 4 stages to a successful web application

  1. Development of the idea, and choosing who is going to develop the product
  2. Creation of the web application
  3. Implementation of product and successful adoption by users
  4. Ongoing support

While there are many sub categories in this list, but it works well as a general overview of the development process.

Development of the idea

For most companies and individuals that are looking to create a custom web application they know what they want to accomplish, but they do not know exactly how to bring their ideas to life. Most people do not say “I want to create a knowledge management system”. They say “communication between departments and certain teams is really bad, we need to make it better”.

The genesis for a web application idea usually comes from two sources

  1. It will solve a specific pain point inside of a company
  2. There is a need for your companies consumers to control and access data in a certain way

The reason that development of the idea and choosing who is going to develop the web application goes hand in hand is because the vast majority of the time the project owner (the person with the idea) is not a technical geek who knows the ins and outs of software development. So he, or she, must look to others to develop their idea into something that accomplishes the goals set out in their vision. Most people have two choices. Find someone inside of the company who can create the product, or find a company who specializes in creating web applications. There are pros and cons to both, but as WebOnyx is a company who specializes in creating web applications these articles will focus on how to choose an outside company to bring and idea to life.

But first before we do that there are a few things about an idea that needs to be expanded upon before we look at how to choose a development company.

Be as clear as you can on what you are trying to accomplish. Write down what the pain points are that you are trying to solve. Give specific example of where the current system fails and what you hope a new system will be able to do. Don’t over think it though. Don’t worry about the details, just get down on paper the general idea of what you want to do. Ask the end users what they like about the current system, what do they really dislike? Lastly what are your metrics for success? What are the statistics that you can look at that will represent a successful project completion. For some companies it will be the click through ratio, for others its user adoption, and for some it is time spent on the site. If you do not know exactly what your metric for success will be that is alright, because a good web development company should be able to help you figure that out.

Which leads us to the next post “choosing a web application development company”

© WebOnyx LLC 2008 | Contact Us