2Wire – CE – Development, Phase 1

2Wire – CE – Development, Phase 1

To ensure effective cross functional communication and full understanding of the direction I was setting, I developed a standard that we called “models”. Models are clickable versions of the experiences that can clearly demonstrate the proposed experience to the various development groups. The models could easily be loaded to a web server and accessed by the teams. This was especially valuable to remote teams in varying timezones. Because of the great clarity and availability of these models across the organization, our product development timelines were shortened by months. For example, the technical publication group responsible for writing user manuals normally had to wait until the first version of software was available before they could begin writing about the product. Leveraging the working models, writers could begin evaluating functionality and working with other groups, like the support organization, shortening their writing timeline from 3 – 9 months to a little as six weeks.

Not only was the model helpful internally, but it could be used to gain early input from the customer. The first version (below) of this model was demonstrated to a particularly impressed customer. The model addressed several of their primary issues and call drivers. Specifically, they recognized the value of the network topology map and ability to rename the SSID. While to a savvy broadband user, these may seem simple issues, to the the majority of this customer base, home networking is still a very scary proposition. This design served as a giant step toward enabling the average consumer to administer their own home network.

Below are the screen caps and a link to a working model

007

006

005

004

003

002

001


Launch the working model