Methods

Creatively Solve Problems

Sometimes a project requires carefully hand-coded solutions. Sometimes it doesn’t. Knowing the difference, and understanding the available options is key to identifying the best solution.

Generate Useful Executive Summaries and Technical Reports

No matter how detailed a report may be, it isn’t always helpful to the business driver. Similarly, a well-worded summary with examples and benefit analyses doesn’t help a developer understand the project better. By having one person produce both executive summaries and technical recommendations, consistency is guaranteed.

Bridge designers and technical teams

Designers don’t always understand the technical limitations and demands of their designs, and engineers aren’t the best at expressing these dependencies to artists. By bridging the gap between the two disciplines, Philip can help teams solve design and development problems together for a given project, and give them the tools they need to understand and negotiate future challenges.

Challenge Clients

For a business driver, one of the biggest challenges is to think about their needs from the outside. When you live with a system or set of needs on a daily basis, you begin to take for granted the knowledge required to understand the problem in context. Once you bring in a team to help satisfy your needs, it is difficult to express to them your situation from square one. Philip has proven success in asking in-depth questions about your process and your needs that help you understand your business better and place your needs in context. Everyone walks away from the table with a better understanding of the business needs, and often, better solutions to the problem arise.

Explore the lifespan

No good development exists in a vacuum. Any system that is developed should aim to evolve and progress into the always-changing future. Talking about the long-term possibilities of a project help developers eliminate assumptions and open doors to future expansion. This effort increases the lifespan of a system, reducing future overhaul and re-development costs.

Plan for phased development

One of the most effective methods in product development is phased development. By releasing a system first with the minimum set of necessary features, then incrementally with each additional feature, the risk of releasing a wholly ineffective system or missing the business opportunity is eliminated. Releasing early and releasing often means that the development momentum is maintained, and business drivers get to see a working system earlier in the development process. Understanding this methodology when planning a project and designing development specs around it make for a happy driver and a happy team.

Measure progress

Once a project has gone into development, many business drivers feel like it’s been shipped off to a black box and will only be returned when complete. The more control-oriented the driver, the more painful this can be for both them and the development team. By having a phased development process and a knowledgeable liaison, this communication gap can be filled. Philip can get involved with your team to understand their progress and challenges, and express these factors to the business driver through regular meetings and progress reports. Any disconnects or setbacks can be worked through in a timely fashion, avoiding suppressed frustration.