STE, simplified technical english, ASD STE100, controlled language, technical texts, technical documentation, ASD Simplified Technical English Specification, non-native English speakers, ASD-STE100 Rules, ASD-STE100 Issue 7 free download

 

How to Fix The Technobabble Snafu

 

Technobabble has become so much a part of our lives that we often don’t see the snafus it can create.  It is a language unto itself:  It is a technical language that is difficult for ordinary people to understand.  Technobabble is well-defined as a type of nonsense that consists of buzzwords, esoteric language, or technical jargon.  There is little question that technobabble has its place.  But the world is changing and the need to communicate information to diverse audiences requires an approach that the entire audience–not just part of it–can understand.  Simplified English might be the answer.

A Technobabble Snafu

Technobabble, Plain Language, Plain English, ASD Simplified Technical English Specification, ASD STE100, ASD STE100 Rules, controlled language, non-native English speakers, simplified technical English, STE writing rules, plain English writing rules, technical documentation, technical manuals, user guides, free downloads

 

“Complex technical instructions can be misunderstood and misunderstandings can lead to accidents. STE makes technical texts easy to understand by all readers”

Some Assembly Required

Some Assembly Required is rarely a reason to buy a product and is often a reason to not buy it.  The directions may be unclear and likely written in text so small that you have to find the Internet version just to read it. It would be a pleasant surprise if  the manual were written in Simplified Technical English that virtually anyone can understand. 

Understandable directions, laid out with graphics that actually relate to the product, help to sell it.  The fact that a manual can be understood by a broad audience does not diminish the product:  It makes it more accessible and more marketable.  In fact, any text written so that it can be understood is more engaging and the content is easily understood.

Technobabble, Plain Language, Plain English, ASD Simplified Technical English Specification, ASD STE100, ASD STE100 Rules, controlled language, non-native English speakers, simplified technical English, STE writing rules, plain English writing rules, technical documentation, technical manuals, user guides, free downloads

 

Avoid Your own Technobabble Snafu!

 

We can help you communicate in Simplified Technical English or just Plain English. Either way, your audience will be engaged in and easily understand your message.

 

CONTACT US

 

A Technobabble Transformation

A group of engineers were set to update a Code written in the last century.  But this would be no easy task because they had no real interest in enabling a wide range of people to crack the Code.  Even the promise of protecting the technical integrity of the Code was not appealing.  But change was coming so they had to make the best of it.  Ultimately, with a few dissenters still unwilling to accept all of the changes, a consensus produced a clear, unambiguous Code.   Their story can be downloaded below.

Leveraging STE

Case study of a Simplified Technical English (STE) conversion in the Engineering sector. The conversion was intended to remove the archaic wording and make the text easier to translate and understand. The transformation resulted in reduced cost and better translations.

Translations

Why not just translate the documentation?

For highly technical documents, Simplified Technical English may be more appropriate than Plain Language.  The controlled language with its technical dictionaries may better transform these texts into clear, unambiguous documentation.  Also, there are times when it is important for all readers to understand the content in English.  Once in English, it can be translated into other languages.

 

“STE was developed to help the readers of English-language documentation understand what they read, particularly when these readers are non-native English speakers.” – ASD-STE100

Translation, however, is not the only consideration here because non-native speakers as an audience is not the only issue.  Documentation in simplified English must also bridge the chasm between native speakers who speak English (or any language) well and those who do not.   This is especially true for training documentation where everyone from upper management to supervisors to workers must be on the same page.  Standard operating procedures, likewise, must be clearly understood by everyone affected by them. 

 

English, Simplified, Might Solve Many Technobabble Snafus

As every business must look for roadblocks that would disrupt their operation, they must also be aware of roadblocks that disrupt communication.  Concerns about reducing documentation content to its lowest level of understanding must be replaced by the intent to make information available to the widest possible audience.  Simplified Technical English and Plain Language can do just that. 

 

 

Simplified Technical English

Simplified Technical English

ASD-STE100, also known as Simplified Technical English (STE), is a specification for writing technical documentation in a simplified language that is easy to understand for a global audience.

This can help improve safety, reduce errors, and increase efficiency in various industries where technical documentation plays a critical role.

-Simplifying the Complex: ASD-STE100 (Simplified Technical English)

STE Lanuage Rules

  • Restrict sentence length to no more than 20 words (procedural sentences) or 25 words (descriptive sentences)
  • Restrict paragraphs to no more than six sentences (in descriptive text)
  • Avoid slang and jargon while allowing for specific terminology
  • Make instructions as specific as possible
    Use articles such as “a/an” and “the” wherever possible
  • Use simple verb tenses (past, present, and future)
  • Use active voice
  • Do not use present participles or gerunds (unless part of a Technical Name)
  • Write sequential steps as separate sentences
  • Start a safety instruction (a warning or a caution) with a clear and simple command or condition.
Before and After Comparison of Plain English Transformation

 

Before

Traditional RPA are the software programs used for simple tasks that don’t require decision making or cognitive activity. These types of bots are also called rule-based systems as they require a set of rules on how to perform a task, where to log in, what data to collect, and where to transfer it.

In general, robotic process automation refers to rule-based bots, which are good for simple tasks and scaling to thousands of automated processes.

CONTACT US

After

Traditional RPA is software programs. These programs do simple tasks. These tasks do not require decision-making activity.

These types of programs are also called rule-based systems. This is because they require a set of rules:

  • How to perform a task
  • Where to log in
  • What data to collect
  • Where to transfer data.

In general, robotic process automation refers to rule-based programs that are good for:

  • Simple tasks
  • Scaling to thousands of automated processes.

Technobabble, Plain Language, Plain English, ASD Simplified Technical English Specification, ASD STE100, ASD STE100 Rules, controlled language, non-native English speakers, simplified technical English, STE writing rules, plain English writing rules, technical documentation, technical manuals, user guides, free downloads

 

Avoid Your own Technobabble Snafu!

 

As Einstein said, “Everything should be made as simple as possible, but not simpler.”  We can help you reach a broad audience without burying the content–and context–of your message.

 

CONTACT US

…in Plain Language

Plain language is grammatically correct and universally understood language that includes complete sentence structure and accurate word usage. Plain language is not unprofessional writing or a method of “dumbing down” or “talking down” to the reader.

 

Plain English

Writing that is clear and to the point helps improve all communication as it takes less time to read and comprehend. Clear writing tells the reader exactly what the reader needs to know without using unnecessary words or expressions. Communicating clearly is its own reward as it saves time and money. It also improves reader response to messages. Using plain language avoids creating barriers that set us apart from the people with whom we are communicating.

-Office of Personnel Management

Plain Language Guidelines Download

Plain Lanuage Rules

  • Write for your reader, not yourself. Use pronouns when you can.
  • State your major point(s) first before going into details.
  • Stick to your topic. Limit each paragraph to one idea and keep it short.
  • Write in active voice. Use the passive voice only in rare cases.
  • Use short sentences as much as possible.
  • Use everyday words. If you must use technical terms, explain them on the first reference.
  • Omit unneeded words.
  • Keep the subject and verb close together.
  • Use headings, lists, and tables to make reading easier.
  • Proofread your work, and have a colleague proof it as well.
Before and After Comparison of Plain English Transformation
Before

Right of use means any authorization issued under this part that allows use of Outer Continental Shelf lands. Right of use means any authorization under this part to use Outer Continental Shelf lands.

This rule proposes the Spring/Summer subsistence harvest regulations in Alaska for migratory birds that expire on August 31, 2023. This rule proposes the Spring/Summer subsistence harvest regulations for migratory birds in Alaska. The regulations will expire on August 31, 2023.

This regulation governs disaster assistance for services to prevent hardship caused by fire, flood, or acts of nature that are not provided by FEMA or the Red Cross.

 

CONTACT US

After

Right of use means any authorization under this part to use Outer Continental Shelf lands.

This rule proposes the Spring/Summer subsistence harvest regulations in Alaska for migratory birds that expire on August 31, 2003. This rule proposes the Spring/Summer subsistence harvest regulations for migratory birds in Alaska. The regulations will expire on August 31, 2003.

This regulation governs disaster assistance for services to prevent hardship caused by fire, flood, or acts of nature that are not provided by FEMA or the Red Cross. This regulation governs disaster assistance that:

  • Consists of services to prevent hardship caused by fire, flood, or acts of nature; and
  • Is furnished by a provider other than FEMA or the Red Cross.

Use Cases for STE and Plain Language?

 

Simplified Technical English

STE addresses difficulties in English comprehension related to complex sentence structures and the following documentation might benefit the most from using it. 

Plain Language (English)

Plain language is communication your audience can understand the first time they read or hear it. A wide range of documentation can benefit from this approach, including:

 

 

 

Why Work With Us?

We are creative, believers in critical thought.  Our layouts are sophisticated and appropriate, effective.  Our work is informative and engaging.  We speak simplified technical English.  Let our technical writing services save you time, money, revisions and failed presentations.

GET IN TOUCH

Do You Want to Turn Your Technobabble into Unambiguous Clarity? 

Let’s Talk

 

 

business plans, business plan writers, business plan writing services, professional business plan, one page business plan, feasiility plan, live canvas, business model, Customer Segments, Customer Relationships, Channels, Revenue Streams, Key Activities, Key Resources, Key Partners, Cost Structure, Value Proposition, target market

A Business Plan For a Reinvented Business

The Challenge

A startup security operations center that planned to enter the healthcare cybersecurity market had created a business plan that was rejected by four different lenders.

The Company was trapped in its vision and had fallen prey to one of the most common mistakes for businesses of any size. Build it and they will come works very well in a movie but not necessarily for a startup. This Company had already invested $3,500,000 into their project because they knew they could get the business. And, they didn’t think they should have to explain how they would get the business. 

They had allowed their vision for the Company to obscure the reality of their situation. A comprehensive business plan that combined vision with validated market and competitive data could likely have precluded this outcome.

Background

business plans, business plan writers, business plan writing services, professional business plan, one page business plan, feasiility plan, live canvas, business model, Customer Segments, Customer Relationships, Channels, Revenue Streams, Key Activities, Key Resources, Key Partners, Cost Structure, Value Proposition, target market

A Security Analyst Station

business plans, business plan writers, business plan writing services, professional business plan, one page business plan, feasiility plan, live canvas, business model, Customer Segments, Customer Relationships, Channels, Revenue Streams, Key Activities, Key Resources, Key Partners, Cost Structure, Value Proposition, target market

Security Training Documents

business plans, business plan writers, business plan writing services, professional business plan, one page business plan, feasiility plan, live canvas, business model, Customer Segments, Customer Relationships, Channels, Revenue Streams, Key Activities, Key Resources, Key Partners, Cost Structure, Value Proposition, target market

Incident Response Flowchart

CyberHealthData was a startup with ambitions to be a major player in the managed security services arena. Their business plan was filled with beautiful pictures of their adaptive reuse of a facility that now housed thirty monitoring workstations as the cornerstone of their Security Operations Center.

They had put their first year revenue at $10,000,000, increasing to $20,000,000 over five years. Their projections were based on the assumption that they would be effectively competing with such high-profile players as Palo Alto Networks and Fortinet. The business plan had been written to obtain funding for the money already spent on the adaptive reuse project and to obtain working capital for the next phase, which was marketing, client acquisition and hiring.

While it is true that the plan lacked any specific, detailed information about the current market, their target market, how the SOC would run, how it would be staffed, how they would find clients, that is not why the business plan was rejected by several lenders. It was quite simple: Every lender felt that the most serous omission was why they thought they were going to be able to compete with companies like Palo Alto and Fortinet.

What they needed was a business plan that was reasonable enough and solid enough that they could obtain funding–a way to make their vision viable.

Need a Professional Business plan?

We can create anything from a lean startup one-page plan to a traditional comprehensive plan not limited by the number of pages.  

The Solution

The nine building blocks of the building model canvas are: Customer Segments, Customer Relationships, Channels, Revenue Streams, Key Activities, Key Resources, Key Partners, Cost Structure, and Value Proposition. This framework was used prior to creating the business plan so that the Company could evaluate their proposed operation holistically, to see how all of the parts fit together. Their vision was set aside for this activity, as the focus was only on the business model framework and not the operations that supported it.

While not part of the original Business Model Canvas concept, the blocks were prioritized according to their importance to the solution.  There were some issues more critical than others that had to be resolved.

Key Activities     

Before anything else, key activities had to be identified.  The only way that the feasibility of the venture could be assessed was to identify what the Company wanted to offer. 

 

Customer Segments

Customer segmentation was next to create a realistic profile of the customers they could expect for their services.

 

Revenue Streams

The anticipated revenue streams were identified:  All of them were related to the operation of the SOC.

Value Proposition

Based on what was in the rest of their business model canvas, the Company created their value proposition.

CyberHealthData had identified their key operations as those relating to a fully-functioning security operations center (SOC); and to the use of the facility for training.  Their customer profile was that of small to medium size healthcare operations in their state, expanding to those in the region.  A separate item in this section, however, was their intent to obtain large accounts such as local universities and hospitals.  Their revenue streams involved two distinct sources:  First were the clients served by the SOC.  Another source identified was education and training of high school students.  The state in which they are located offers a $7500 stipend for cybersecurity training when the facility is qualified.  Their facility qualified. That said, their financial projections did not include the student training because they considered it to be an insignificant part of their revenue. Their value proposition centered on the fact that the facility had been constructed and that they had hired cybersecurity specialists as management personnel.  

The solution resulted from a realistic assessment of their business model canvas and the use of market data that would better enable them to make a decision.  A critical consideration was their competition.  A random survey was done of small and medium size healthcare facilities in the state to determine what cybersecurity measures they had in place.  Over 75% of them used online managed service providers.  Larger organizations such as university health centers had their cybersecurity programs developed by firms such as Palo Alto Networks and Fortinet.

At this point, the Company had to reevaluate the model they had created so that they could present a viable proposal to lenders.  The model was then completely restructured.  The decision was made to come up with a model that did not include providing managed SOC services.  

There are 1.12 million high school students enrolled in the state in 2024.  Each of those students potentially has a chance to receive one of the $6500 stipend ($5000 of which would accrue to CyberHealthData).  In operating year one, if the program captured only .04% of those student as trainees, annual revenue would be $2,500,000.  While this was a quarter of what they had originally projected, it was based on a solid business model that had the potential to grow as reinvestment into the Company was made.  The facility currently houses 10 security monitoring stations.  The new plan was to operate this as a training center for 50 weeks a year with 500 students completing the hands-on training and some remote study.  

The value proposition then increased dramatically.  In addition to a stable operation, the facility would provide job training for the many cybersecurity incident response analyst positions that remained unfilled.  It would also provide an incentive to keep students in school since the high school population was rapidly decreasing.  

The Result

Actionable Business Plan

The most important thing that resulted from this process was an actionable business plan that got the Company the funding they needed–even if it was not what they originally wanted.

Depending on their size, our business plans may include many sections that are not routinely found in other plans.  But we believe they are what makes our plans so successful:

  • Reasonable business model that is viable
  • Area-specific target market analysis–whether the market is for an Internet based business or a local business
  • Market analysis using current information
  • 2024 demographic information
  • Risk assessment and scenario planning
  • A mini-economic analysis to show the impact of an operation on the market and population in which it operates.

Business Plans

       Problems Solved

  • Business Model:  A sustainable business model evolved that would ensure a profitable, stable operation that could weather economic variances.
  • Target Market:  An entirely new target market was identified but it was one that already existed as an available market and one for which the Company was already guaranteed a share.
  • Competition:  The new model eliminated any concerns about how the Company would compete in an already-crowded arena with many high-profile players.  With only one other vendor in the state offering similar training programs, they could establish a much higher profile in this arena.
  • Revenue streams:  This source of revenue was one that could be more easily validated contracts, letters of authorization, etc.
  • Physical Facility:  Even with the reduced level of revenue, it was reasonable enough that lenders would believe that payments could be made from projected revenue.
  • Vision:  They could now create a vision and goals that were attainable.

Strategic Plans

This was a traditional, comprehensive plan but the Business Model Canvas is often used as the basis for a lean startup one-page plan, which we also create.  The names and locations were changed.

 

 

Why Work With Us?

We are creative and logical, believers in originality and critical thought.  Our layouts are sophisticated and appropriate, effective.  Our work is informative and engaging.  Let our technical writing services save you time, money, revisions and failed presentations.

HOW CAN WE HELP?