- Most Recent | Since 2004
- List View
- Archive
- February 2, 2010
Groundhog Day Resolutions 2010: Kickoff
February 2, 2010Read more
SUMMARY: It’s time for the 2010 Groundhog Day Resolutions! I review the past three years of resolutions and create a 2010 master resolution that hopefully will give me a direction for the year.*
(more…)
- January 28, 2010
Kanban, Event Modeling, and GTD
January 28, 2010Read moreSUMMARY: I attended a “Scrum Club” meeting to learn about agile software development methods and kanban, and noted the similarity to the GTD productivity system. Kanban boards are particularly interesting to me, as they make abstract processes more visible through the use of physical artifacts. (more…)
- January 27, 2010
Design Agency Process Diagram
January 27, 2010Read more
In Monday’s post I went through a process of recentering myself, and identified four areas to focus on and track. The trickiest one was DESIGN AGENCY, because there are a LOT of different tasks.
I just finished creating a “process diagram” that outlines a high-level roadmap of agency operations; just about any task I can think of fits somewhere the diagram. You can read about and download the PDF over on the Agenceum Blog, which is where I am running my “open design agency” experiment. Although this diagram is labeled for Agenceum, it really is for ALL of my design-related business activities.
Read more about the diagram on the Agenceum blog.
- January 26, 2010
Agenceum System Process Diagram
January 26, 2010Read more
Last weekend I was thinking a lot about the various tasks that needed tracking as part of the Agenceum project load. It had gotten to the point where I was starting to worry if I was forgetting something, and it also seemed that I needed to formalize some processes. The idea of making a map of everything seemed useful, so I started sketching it out on Sunday, and have been refining it over the past couple of days. The result is a fairly complete process list of Agenceum business functions. In short, it’s an idealized process guide to everything that has to get done at Agenceum, based on my prior experience at various small agencies and my own freelance practice.
The general idea is that any task that I’m doing on Agenceum (or David Seah/Associates, for that matter) corresponds to one block somewhere on this diagram. Once I know what block that is, I can then see what needs to happen next. Eventually, I can create tickets for each of these tasks, and use this overall process diagram to manage the workflow.
Some other notes:
- In general, tasks start from the left and move on through the right until results are achieved. The result may feed into another process; for example, many of the marketing processes result in an INQUIRY, which can then be handled by the INQUIRIES process line.
- Several tasks have iterative cycles baked into them, for example the typical design-review-refine cycle.
- Also, the processes are roughly ordered from top-to-bottom as outward-facing to inward-facing activities.
- Each box has a word or short phrase that evokes what needs to be done. So theoretically, the way to use this diagram is to wonder what the hell you’re doing, look at the process diagram, and then see what you need to be working toward. There is also some implied creative strategy baked into some of the processes, which I could write about at length but will save for some other time.
- The first four MARKETING lines have a vertical hash line that indicates that you can jump from any of those four starting points to a different tactic to generate inquiries.
- For the FINANCIALS and EXECUTIVE lines, the left-to-right process is arbitrarily defined. I tried to think of the most important things to be mindful of with regard to these functions as I understand them. Your mileage may vary.
You can download the latest version of this file here as a PDF: » AgenceumSystemProcesses.pdf
- January 26, 2010
Tuesday Evening Staff Meeting
January 26, 2010Read moreI visited five different locations to work today: home, Starbucks, Ashish’s office, Bonhoeffer’s (a local coffee shop), and Sid’s studio (with no Internet). So I’m just getting to the Staff Meeting report.
Current Business
I’m getting close to finishing two of the projects, now that final content is in. What is interesting is that every one of these tiny projects takes many weeks of calendar time to complete, with scattered bursts of activity. I could complain about that, but instead let me just list the criteria that small client projects seem to share, so I can design a process around them:
- These projects are very “spiky” in terms of activity. When the project starts, there’s a surge of activity. Then, as time goes on, the urgency ebbs as other priorities take over; a new job-related priority springs up, difficulty in finding time, changes in direction. The low-cost website is, perhaps by nature, a non-priority purchase because the amounts involved are small. This leads to rescheduling and delay. It’s difficult to run an efficient creative production engine with that kind of input, so I think I need to design a spiky creative production engine that is modeled after a fast food sushi system in reverse; empty trays float around the track, representing available work units on certain days. The enterprising client needs to load the tray with their work before production begins. The main idea is to make it apparently that there are limited production slots, and that timing and preparedness is required. This would also help even out my own planning; being reactive to client needs that can strike at any time, without a maintenance or retainer structure in place, is tough on scheduling and energy.
- Clients often don’t have their own project managers. I have not been offering project management beyond what I have on Basecamp, because the least fun thing in the world I can imagine is chasing after other people’s projects when they are not ready to move. It’s not their fault, but it takes time, and that requires money that is not in the budget. To handle this, I might just have to add a project management fee, so people feel they are paying to be managed. Often times, it’s a relief. I may call this a continuity maintenance fee for projects that linger beyond the original date, if the client needs help getting the ducks lined up in a row. This would be very minimum project management, consisting of use of the Basecamp area.
- Content Quality Assurance is implicitly included in this as well, in areas where the client feels they aren’t expert. This includes supporting content creation, such as photography, logo design, copy writing, marketing, and business strategy. The website often can’t go live until this is done. To identify this as a hangup, I am going to create a website preparedness checklist for clients, with boilerplate copy and links to resources to pound them out. I can also provide custom services at a higher rate.
- Website Maintenance I’ve talked about. I think I have some solutions in place.
Agenceum Processes
There is enough stuff going on that it’s becoming a significant mental burden. This is the combination of scheduling creative time, sending off status emails, doing the creative and technical work away from distraction, and making sure I’m not forgetting anything. And this is with only a handful of clients. On top of that, there’s the need for R&D and expansion of all the support material for each client. This material is reusable, but it’s a drain on my mental capacity the more I have to switch between clients. Ideally, I handle all clients and projects the same, which means I am feeling the need to establish a methodology.
I spent the past day writing up and distilling what I know about web agency processes into a diagram that will help me contextualize everything I’m doing. I’ll post that next as a separate article.
On Deck This Week
- Finish integrating Chelsea’s website with new content and photos
- Convert Chelsea’s Website to CushyCMS or something similar
- Logo work: Chelsea
- Logo work: Leo
- Catch up with stalled projects, get new status update, evaluate need for new support docs and methodologies.
- Create small website kit, based on a single template.
SUMMARY: It’s time for the 2010 Groundhog Day Resolutions! I review the past three years of resolutions and create a 2010 master resolution that hopefully will give me a direction for the year.*
In Monday’s post I went through a process of
Last weekend I was thinking a lot about the various tasks that needed tracking as part of the Agenceum project load. It had gotten to the point where I was starting to worry if I was forgetting something, and it also seemed that I needed to formalize some processes. The idea of making a map of everything seemed useful, so I started sketching it out on Sunday, and have been refining it over the past couple of days. The result is a fairly complete process list of Agenceum business functions. In short, it’s an idealized process guide to everything that has to get done at Agenceum, based on my prior experience at various small agencies and my own freelance practice.
The general idea is that any task that I’m doing on Agenceum (or David Seah/Associates, for that matter) corresponds to one block somewhere on this diagram. Once I know what block that is, I can then see what needs to happen next. Eventually, I can create tickets for each of these tasks, and use this overall process diagram to manage the workflow.
