What do you do?
We create software delivery systems: products and services to make development organizations leaner and faster
How many pages of print design do you need?
List the size requirement(s) for your print design
What is your industry?
Describe the target audience for your print design
A technical executive - CIO or CTO. Someone who is looking to get software out the door, faster.
What 3 things would you like to communicate to your audience through your print design?
Speed, Agility, Results
Style and Concept
What print design styles do you like?
What colors do you want to see in your print design?
Orange. See http://www.stelligent.com/. Include other colors, but this is the main color.
What colors do you NOT want to see in your print design?
What adjectives should best describe your print design?
Speed, Agility, Results
How will you use the print design?
Distribute to prospects and clients
What content must be included in the print design?
An "assembly line" that demonstrates taking raw source code and hardware (computer machines) and continually converting into a functioning software system with every change applied by software developers and systems engineers. The concept is to make the process of delivering a software system analogous to an automobile manufacturing assembly line.
1) continuous_delivery_1.jpg shows the "boxes" demonstrating the parts of the process/system and the order of the "assembly line". Notice the arrows. **It's only an example and use it more for the information to display and not specifically how to show it**.
2) continuous_delivery_2.jpg can be used as an example of what this "assembly line" could look like.
We're very open to other concepts, but there are two approaches that come to mind:
Option 1? Use something like the "box" being manufactured as shown in the continuous_delivery_2.jpg for each part of the process (a metaphor for delivering software). The limitation with this approach is how to graphically deal with things like "project management", "issue tracking", etc. as they aren't directly related to the act of making the box as shown in continuous_delivery_2.jpg
Option 2? Use icons to represent the purpose of each of the boxes, such as issue tracking, database, machine, project management, continuous integration, etc.
Don't use stick figures
We're sure there are other approaches that could work great, but these come to mind.
No Files Added