Writing a technical book
Discussion
I'm considering writing a non-fiction book covering some of the practical lessons I've learnt in the past 20 years of my career in IT Operations. There are a very large number of theoretical books covering my field (not to mention ITIL, Prince etc) but hardly any practical ones that could help IT Operations managers starting out, or wanting fresh perspective/ideas. So not talking frameworks but actual things you can do to organise IT. I've certainly felt it a challenge when sourcing training to find anything that isn't too high level/hypothetical.
And it won't be too technical, sort of a mid point between theory and full implementation guides. I'd cover things like procedures/documentation/business continuity/DR etc.
I thought I'd bounce it off the sometimes brutal PH massive. Is this the stupidest idea ever? I'm certainly not recognised in my industry but I am very successful in my role.
My other concern, I've been with my current employer for 10 years, one of the biggest companies you won't have heard of (my remit is just UK) so many of my observations/suggestions will be based on what I have put in place and the best practice I've seen.
I want to make sure I don't stray into an IP issues, say I draw up templates that are similar to ones I've produced for my company (on their time) - is this just asking for trouble? Its easy to get caught up in an idea and not see that its a can of worms.
Should I actually do this it may not even sell a copy but will be an interesting task and I'm already working on a fiction book.
Thoughts/castigation welcome!
Also, anyone else written a non-fiction book? Experiences welcome!
And it won't be too technical, sort of a mid point between theory and full implementation guides. I'd cover things like procedures/documentation/business continuity/DR etc.
I thought I'd bounce it off the sometimes brutal PH massive. Is this the stupidest idea ever? I'm certainly not recognised in my industry but I am very successful in my role.
My other concern, I've been with my current employer for 10 years, one of the biggest companies you won't have heard of (my remit is just UK) so many of my observations/suggestions will be based on what I have put in place and the best practice I've seen.
I want to make sure I don't stray into an IP issues, say I draw up templates that are similar to ones I've produced for my company (on their time) - is this just asking for trouble? Its easy to get caught up in an idea and not see that its a can of worms.
Should I actually do this it may not even sell a copy but will be an interesting task and I'm already working on a fiction book.
Thoughts/castigation welcome!
Also, anyone else written a non-fiction book? Experiences welcome!
There are a multitude of options now for self publishing especially with ebooks and on some ebooks you can embed a bunch of interactive and multimedia elements.
I have written a couple of Project management study guides, and self pubbed. After picking up a few tips from working at a big publishers.
Not sure about the IP side, probably worth checking your contract.
I have written a couple of Project management study guides, and self pubbed. After picking up a few tips from working at a big publishers.
Not sure about the IP side, probably worth checking your contract.
I'm currently doing the same.
Don't expect JK Rowling type levels of financial income from the endeavour. Where the financial benefit comes is in the added credibility you attain having had a book published about the subject from which you earn your living from. You may get some paid-for invitations to speak at conferences. Point here is don't go thinking you'll retire on the proceeds.
Self-publishing is a more viable option than it was in past but will negatively impact on credibility. You should really strive to find a publisher and if there is a market for your book, they will be able to maximise the opportunities better than you.
Before you lock yourself away and start writing, it's worth doing a couple of things first.
1. Is there a market for the book? You can treat books of this nature like a business. Research the market; are there any other similar books of a similar topic out there. If there is, what can you provide that is different or better. If there isn't anything out there; why?
2. Don't write the whole book. Write one chapter / section to the point of perfection. Then write two précis of the whole book; one should be a two paragraph description of what the book is about all on one side of A4. The other can be a little more expansive. Then list the the table of contents and write a short, one page bio'. This is what you then tout round to the publishers. If one of them bites, that's when you knuckle down to write the whole thing.
3. Only target publishers that are already publishing books in your field.
As for submitting to publishers, there's two options. You can either send yourself or you can get an agent. An agent will of course take a cut but they know the score, know how to approach them and how the system works.
If you do submit yourself, you can expect every response to be negative but keep pushing. One chap I know sent the same précis to the same publisher each week for 10 weeks, each with a slightly different font and paper. On the 10th submission, they accepted the title. They have teams of people who assess submission and a lot comes down to the individual reviewing them.
As for the content, a good tip given to me is never assume you know it all (even if you do). It is very easy for it to become autobiographical rather than technical. To avoid this, you should include many references to the work of others and direct quotes from speaking to others. For example, if you are describing using a process developed by Dr John Smith of Somesuch University...go and interview him to establish how he developed that process and include this in the book.
As for the issue of IP, this is tricky and care should be taken. I don't know your industry so cannot comment on the intricacies but clearly, if you have been employed to develop something that your employer financially benefits from, then you shouldn't give away this in the book. This is why publishers are the best route as they will have legal teams to sort all of that out.
HTH
Good luck!
Don't expect JK Rowling type levels of financial income from the endeavour. Where the financial benefit comes is in the added credibility you attain having had a book published about the subject from which you earn your living from. You may get some paid-for invitations to speak at conferences. Point here is don't go thinking you'll retire on the proceeds.
Self-publishing is a more viable option than it was in past but will negatively impact on credibility. You should really strive to find a publisher and if there is a market for your book, they will be able to maximise the opportunities better than you.
Before you lock yourself away and start writing, it's worth doing a couple of things first.
1. Is there a market for the book? You can treat books of this nature like a business. Research the market; are there any other similar books of a similar topic out there. If there is, what can you provide that is different or better. If there isn't anything out there; why?
2. Don't write the whole book. Write one chapter / section to the point of perfection. Then write two précis of the whole book; one should be a two paragraph description of what the book is about all on one side of A4. The other can be a little more expansive. Then list the the table of contents and write a short, one page bio'. This is what you then tout round to the publishers. If one of them bites, that's when you knuckle down to write the whole thing.
3. Only target publishers that are already publishing books in your field.
As for submitting to publishers, there's two options. You can either send yourself or you can get an agent. An agent will of course take a cut but they know the score, know how to approach them and how the system works.
If you do submit yourself, you can expect every response to be negative but keep pushing. One chap I know sent the same précis to the same publisher each week for 10 weeks, each with a slightly different font and paper. On the 10th submission, they accepted the title. They have teams of people who assess submission and a lot comes down to the individual reviewing them.
As for the content, a good tip given to me is never assume you know it all (even if you do). It is very easy for it to become autobiographical rather than technical. To avoid this, you should include many references to the work of others and direct quotes from speaking to others. For example, if you are describing using a process developed by Dr John Smith of Somesuch University...go and interview him to establish how he developed that process and include this in the book.
As for the issue of IP, this is tricky and care should be taken. I don't know your industry so cannot comment on the intricacies but clearly, if you have been employed to develop something that your employer financially benefits from, then you shouldn't give away this in the book. This is why publishers are the best route as they will have legal teams to sort all of that out.
HTH
Good luck!
Thanks for taking the time, both of you - some really interesting pointers! On the IP front, it's nothing I've developed for my company, just best practice I've put in place and I think it could be worth sharing that experience as I found little guidance on this subject over the years.
And no, I don't expect to make any money, let alone lots - more interested in the challenge.
Thanks again, I feel more positive about exploring the idea.
And no, I don't expect to make any money, let alone lots - more interested in the challenge.
Thanks again, I feel more positive about exploring the idea.
Gassing Station | Jobs & Employment Matters | Top of Page | What's New | My Stuff