June 20, 2011
No Comments
I often tell my students that as technical communicators, we are professional gadflies. It is our job to buzz persistently, and bite when necessary, to get certain things done. We cannot move forward with documentation on a product that is languishing, so we interact with the developers to see how things are going. We ask for prototypes and working versions. We query them about deadlines, especially “When’s code freeze?”.
We often become de facto project managers on the projects to which we’re assigned. In managing our documentation projects, we encourage, inspire, assist, and even require others to meet their production and development deadlines so we can take that deliverable and add its information to our documentation. Another rule of our craft is that a product never, never, never is delayed for release because of documentation. When that product is ready to go, so is the documentation, and often it’s that the docs are done and just waiting on the final touches to the product. (Cleanup, not changes.) (more…)
June 7, 2011
No Comments
Endorsed Development, a new way of attracting a market for products we want to create.
Since the Stone Age, products have been developed based on need. They were meant to solve problems and assist us in completing tasks. To begin with, it was survival tasks, soon followed by transportation tasks, trading tasks, and leisure tasks. In design, form closely followed function.
As we developed greater technical skills, we began to innovate. We refined designs to be more usable and more attractive. Occasionally, because of cost and demand for the products, designs were adjusted based on ease of manufacture. When we had to get something to market quickly, we concentrated on making it work and shipping it as soon as we could.
Design-Driven Development
With automation and the assembly line, speed of manufacture was handled so we concentrated once more on making things attractive as well as functional. We were still tied to the products-as-solution imperative, but we could add features that we thought were fun. Features became selling points, even though marketers kept reminding us that it was benefits, not features, that sold products.
(more…)
Filed under: Business, Connection, Improvement, Marketing, Networking, People, Products, Social Media, Twitter
Tags: Connection, Development, Marketing, Networking
June 4, 2011
1 Comment
Contractors and freelancers are often asked to name their hourly rate for jobs, or state their salary expectations. Depending on the industry and the type of work you’ll be doing, rates can vary widely. I personally have found that for jobs I can properly scope, quoting a flat rate for the entire job is more worthwhile. But sometimes you need to know what figure to quote for work that will be billed at an hourly rate.
Here are some ideas that have worked for me:
- Determine how much you’re willing to do the job for. You will have a sense of how much it costs you to work (transportation, child care, clothing, lunches, etc.) and about how much per hour you’d need to earn to make it worth your while to take the job. That figure is your low end, rock bottom amount. See what they’re willing to offer above that figure. If they offer less, you must realize that you’ll be losing money by taking that job. Unless there’s a compelling reason to take that particular job, or if you have some other way of making up your shortfall, tell them thanks but you really need to be making at least $XX.00 per hour.
(more…)
