A typical process flow for a piko.biz project might look like this:

The first step in any project is to define the set of goals. These are developed by speaking with the client, reviewing any relevant material, and conducting other research and interviews as might be necessary. In larger enterprise environments, we also want to reach out to the client's technology support staff early in the project timeline.

A (formal or informal) statement of goals is then prepared for the client, along with other relevant information gathered during the information collection stage. This summary is our first major milestone and is used to confirm the goals, expectations, schedules, deliverables, and budgetary boundaries. The summary review conversation can result in further refinements to the original goals and scope of work. A client may request a revised proposal for the project prior to granting approval to proceed.

The next milestone is the design phase, where different design options are presented to the client. This set of proposed designs is usually created in an "electronic pasteboard" format allowing the client to suggest, critique, and recommend early in the process.

After a design has been approved, we build a "clickable" and easily accessible prototype for the client to view as the next phase of the project. This tangible prototype provides confirmation that we are moving in the right direction, and an opportunity to provide feedback relative to the look, feel, and structure of the solution. Approval of the prototype concept is a major milestone and required before moving to the development phase.

In this next phase, the development is completed using technology that is appropriate to the audience, the problem space, expected usage patterns, client environment and, of course, the project goals. Web based deliverables are tested on a variety of browsers and versions on the Windows and Macintosh platforms. The solution is made available to the client for final approval before entering the testing phase.

During the testing phase, we work closely with our clients and their technology staffs to develop test plans or gradual rollout methodologies that are appropriate to the project. Once the solution is tested and approved by all, it is ready for production.

After the project is completed, we remain available for follow ups and edits that may be needed. Longer term, we encourage our clients to involve us in a regularly scheduled site review to ensure that both the content and the technology remain fresh and timely.