Pushing-new-technology-the-hard-way-Part3

Pushing technology the hard way (Part3): How to do an interesting tech presentation

In the previous part of this blog, we set up immudb as replicated StatefulSet in Kubernetes. Now it is time to talk about our work. The perceived performance of a project or an employee is very important inside large organizations. That’s why we have to present our work properly. Interesting technical presentations are rare because it is very difficult to explain complex concepts in an entertaining way.

Know your audience


One of the most important pieces of advice for tech presentations is that you have to know your audience. Are you doing the presentation for managers, engineers, or salespeople? Your audience can also be mixed. Knowing your audience is crucial in order to get their attention. For example, students are not the right audience for a sales presentation of enterprise software. As a general rule of thumb: the presentation should be less technical the more people are in the audience. Learn how to simplify things in a digestible manner by explaining the topic to people who are not familiar with the field or the terminology.

Also, you should think about these questions: Why should your audience listen to you? What do you expect from your audience? The attention of an audience is a valuable thing. They are spending their time with you. Be respectful by doing good preparation and an interesting presentation. Last but not least you have to have a goal. Do you want to inform people or ask for collaboration and resources? Make it clear. You are a butler serving information for your audience on a silver platter.

The introduction

A really good introduction is key to captivate your audience. The attention span of most people today is very narrow. Your audience could simply get out their phones if your presentation is not interesting enough. Online presentations make it even worse. People will not listen to your presentation if it is boring, so the best way is to get their attention right from the start. I love to structure my presentations by the why, how, what method. Now let’s look at an example of presenting a cybersecurity solution built on immudb:

  1. confidently introduce yourself
  2. Tell your audience why you are here. That can be done by quoting an interesting fact. For example: “In 2020, the average business cost of a cyberattack is $3.86 million and it takes over 200 days to detect the breach.” (IBM). Or start by telling a story. An interesting story in this field is the SolarWinds hack of 2020.
  3. Offer a solution. Shortly explain how the right solution looks like.
  4. What can you do to solve the problem? Provide a short, clear, and interesting agenda.

Facts and linked stories can almost always be found in the infos of the manufacturer. You don’t have to be super creative. Just do some research!

Main part and techdemos

The main part is really about presenting the solution with the most important details. Try to keep the attention up. Only show clean slides without unnecessary information. Be concise and simplify the charts as much as possible. Don’t lose your audience here. Tech demos are very popular in order to get some interaction with the audience. They are also very risky because things can go wrong. Maybe that’s why they are generally more interesting than slides. You should always try to set up your tech demo redundantly. For example, immudb could be demonstrated running locally on your laptop, hosted on a server or cloud environment, or with the immudb playground. The tech demo is a great opportunity to choose entertaining examples and to interact with the audience.

Outro

I love to end the presentation by displaying keywords or a collection of the most important slides on the final slide. People will remember what has been said more easily and are more likely to ask questions. Every good presenter wants feedback. That’s why you have to allow time for questions at the end. Don’t overrun, your audience will hate that. Last but not least: close with a summary. It is important to have the last word to save your presentation from being ruined by a bad question.

Summary

In this blog, we talked about doing a tech presentation in an entertaining way. Don’t be too hard on yourself when doing presentations. It is oftentimes more authentic and sympathetic if there are some signs of stage fright.

immudb

BUILT ON THE FASTEST
IMMUTABLE LEDGER
TECHNOLOGY

Open Source and easy to use in new applications and easy to integrate into existing application.

MOST POPULAR

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.