FAQs

 

How does synthesis differ from technical writing or editing?

To a first approximation, synthesis, unlike technical writing, cannot be taught. It combines a lifetime of experience with natural proclivities and a wide and deep knowledge base. It requires significant skills in critical thinking.

In the context of my activities, a synthesist must be familiar with not only the topic under discussion, but the basics of the science and technology that underlie the research, phenomena, or technology being addressed. Synthesis presumes significant knowledge of the nature of the organization, its role(s) in the larger context, how the work being addressed fits into the larger body of knowledge, and hands-on experience with as many aspects of the topic as is possible. Synthesis requires exploring the universe of applicable materials, deciding what is appropriate for the target communications vehicle, collecting and collating these materials, and then synthesizing a suitable document, where there was no such document before. Synthesis involves many of the same tools as technical writing and uses editing as one of its tools, but more commonly the activity involves creating a new, usually highly complex document from existing material. A synthesist will apply editorial acumen during the process, and will often work with one or more editors (see below).

Technical writing has much in common with synthesis, but the key difference is in the amount and nature of data and information being dealt with, and the contexts in which the work must be placed. Most often, a technical writer will have familiarity with the topic, excellent research skills, and an ability to generate a suitable document or other communications medium. But hands-on experience with the topic areas is not always available.

Among myriad other activities, editing commonly involves taking existing material and working with it to improve it. Top editors have enough topic-related background to know when logical flows are lacking, where information is needed, and when and how structure needs to be changed to make the document into an effective one. Usually, a marked-up (and often modified) document is returned to the author(s) for further work. Another editing pass is then often instituted.

 

After an initial mutual introduction to see if we really can work well together, we will define the parameters and boundaries of the work you need done and my proposed response. We will establish the nature of the work, what are our respective roles and responsibilities, the schedule—including drafts, review and commentary, my responses, etc.—the nature of the final deliverable, and when it is due. We will also discuss fees and payment schedules.

Depending on the nature and scope of the work you need done, I may propose a solution that goes beyond my singular activities. I would investigate what other resources might be needed to ensure a quality and timely response to your needs, and propose the team approach to you.

After we determine all the components (as outlined above), just turn me loose on your project. I prefer to work in a “black-box” mode (i.e., feed me input, I’ll give you quality output), but be assured that I will comply with all agreed-upon interim reporting requirements. And, if I have any problem—be it technical, budgetary, schedule, or anything else—rest assured that I will contact you as soon as I surface it, or determine that I cannot deal with it without your input.

 

Nondisclosure

We can build appropriate language into a consulting or services agreement, and/or we can negotiate a nondisclosure agreement (NDA). I do this routinely. Please note that I have worked with many types of organizations over the years, some with very stringent requirements for data/information handling. I never discuss my projects with anyone about whom you have no knowledge; you’d preapprove potential teams that I may form to respond to your project needs, and all such team members would be subject to my umbrella NDA or I can enforce individual NDAs, should you wish. Regardless, I never use material from one client for another’s projects.  Hard copy material is shredded after use.

Electronic Document Storage and Use

Operationally, all working materials are stored in encrypted volumes on my disk drives that are unloaded whenever I leave the office. Project-related working and interim material will be deleted from my disks upon final delivery, should that be your wish, although I prefer to retain a copy of the final deliverable.

Network Connectivity

My Internet connection is encrypted line-of-sight wireless. All Web connections are made with the secure https protocol where target servers support it.  Email connections are made with TLS (secure-to-dedicated-port) protocols. Should I need to work offsite, I always use VPN tunnels to connect to whatever servers I need to access. We can arrange for encryption for electronically transferred input material and interim deliverables and drafts.

Please contact me should your needs not be met with these procedures.

 

We can establish fees on a per-hour, per-task, or per-project basis. Generally, I receive an initial fee to begin the work, with mutually agreed-upon milestone-related payments thereafter. For longer-term projects, and particularly for those with per-hour fees, I bill in arrears on the first of the month, i.e., I will bill you for work done the previous month. Payment is expected within 30 days of receipt of the invoice. A penalty of 1.5% per month thereafter will be levied for invoices unpaid after 60 days. Payment will be by company check.

Contacting me via email to info@sciential.com is the best way to go, for reasons that will follow. Or, you can call me at +1.406.284.4150.

I request email because it allows you to clearly define your project or task in a way that I can examine in detail before responding. This can be done by phone, and I invite a preliminary call, should you be more comfortable speaking with me before generating such a potentially detailed analysis. My basic approach is, “Whatever works for you!”; I just thought I’d get my vote in early.

In your introductory email, please let me know the nature of your task or project, where it fits into my published and potential service areas, and the period of performance, i.e., how soon you’d ideally like to begin, and when the final deliverable is due, and how best to get back in touch with you, i.e., email or phone. If the latter, please include a number and time(s) when I can best reach you. Please include any other information you think I should know about to allow me to formulate a response, to allow us to best use our respective resources.