Professional Documents
Culture Documents
Explaining The Future How To Research Analyze and Report On Emerging Technologies Sunny Bains Full Chapter
Explaining The Future How To Research Analyze and Report On Emerging Technologies Sunny Bains Full Chapter
sunny bains
1
1
Great Clarendon Street, Oxford, OX2 6DP,
United Kingdom
Oxford University Press is a department of the University of Oxford.
It furthers the University’s objective of excellence in research, scholarship,
and education by publishing worldwide. Oxford is a registered trade mark of
Oxford University Press in the UK and in certain other countries
© Sunny Bains 2019
The moral rights of the author have been asserted
First Edition published in 2019
Impression: 1
All rights reserved. No part of this publication may be reproduced, stored in
a retrieval system, or transmitted, in any form or by any means, without the
prior permission in writing of Oxford University Press, or as expressly permitted
by law, by licence or under terms agreed with the appropriate reprographics
rights organization. Enquiries concerning reproduction outside the scope of the
above should be sent to the Rights Department, Oxford University Press, at the
address above
You must not circulate this work in any other form
and you must impose this same condition on any acquirer
Published in the United States of America by Oxford University Press
198 Madison Avenue, New York, NY 10016, United States of America
British Library Cataloguing in Publication Data
Data available
Library of Congress Control Number: 2018948523
ISBN 978–0–19–882282–0
DOI: 10.1093/oso/9780198822820.001.0001
Printed and bound by
CPI Group (UK) Ltd, Croydon, CR0 4YY
Links to third party websites are provided by Oxford in good faith and
for information only. Oxford disclaims any responsibility for the materials
contained in any third party website referenced in this work.
For Stuart and CJ
PREFACE
W
ill this new technology solve the problem its inventors claim it
will? Is it likely to succeed for any application at all? What is
the right technical solution for a particular problem? Can we
narrow down the options before we spend a lot of money on develop-
ment? How do we persuade our colleagues, investors, clients, or readers of
our technical reasoning?
Whether you’re a researcher, a consultant, a venture capitalist, or a
CTO, you will need to be able to answer these questions systematically
and with clarity. Most people learn these skills through years of experi-
ence. However, they are so basic to a high-level technical career that they
should be made explicit and learned up front, making the whole learning
process more efficient.
This book will provide you with the tools you need to think through
how to match new (and old) technologies, materials, and processes with
applications. Specifically, the first chapter covers the questions you need
to answer, while the second looks at how to structure your research to
answer them and points you to different resources that you might not
have thought to use. Chapter 3 discusses how to decide whose opinions
you should trust, whether in writing or in person, and whose you should
treat with caution.
In Chapter 4, we switch gear and focus on technical analysis, bringing
together all the information you have gathered into something meaning-
ful. To help you visualize what needs to be done here, this section includes
several canvases that can be blown up and used to structure your material.
These will help you identify opportunities and difficulties, eliminate dead
ends, and recognize where pieces of the puzzle are missing and you have
to do more research.
The final three chapters will help you think about how to communicate
your conclusions. Chapter 5 starts with the most important part of the
communication process—the audience—and how it dictates everything
Preface | vii
from how you set the context for your report, to the kind of jargon you
use, to the depth of explanation you go to. In Chapter 6, the critical basic
steps of a technical argument are covered, along with clear, pragmatic
explanations of how they must be ordered in order to bring your audience
along with you.
Chapter 7 essentially covers how to be believed. It teaches you how to
second-guess your audience’s prejudices, how to avoid coming across as a
salesperson, and how important it is to be honest about issues that go
against your argument so that your readers will learn to trust you. It also
provides advice on how to guide your audience through difficult material
by using good writing and clear signposts.
Finally, the book concludes with a case study showing worked examples
of how all these techniques can be used in practice.
What you do with these skills is up to you. You might use them to
ensure that you position your work to be ripe for funding opportunities,
or to figure out who your potential customers are. Alternatively, you
might use them to determine whether the claims made for a particular
technology are valid: is it valuable, or is it vaporware? This book will teach
you how to find the right information, ask the right questions, and inter-
pret what you find without being swayed by hyperbole and PR.
Whatever your end goal, this book will help you to make your case in clear,
logical reports that are spoken and written at the right level for your audience.
Audience
The book is written for people with some kind of technical (engineering
or science) background. It’s ideal for students, from motivated under-
graduates to masters and doctoral candidates, in that it will help give you
a framework for thinking about your subject, as well as tools for research,
analysis, and technical communication. For graduates taking their first
steps into consultancy, start-ups, or tech-sector investing, the book high-
lights the real-world issues that determine success in technology but are
often neglected at university, as well as introducing you to some important
audiences you will have to persuade in order to achieve success. Finally,
the book will suit mid-career scientists and engineers moving from the
lab to technical management and other careers that demand they be more
strategic in their thinking.
viii | Preface
For more information
Once you’ve finished reading, you can get more resources via our website.
These include summary videos highlighting key concepts; downloadable
versions of the canvases used in the book; instructions, templates and
check sheets for writing different kinds of documents and presentations;
and more. Go to http://explaining-the-future.org and get full access by
logging in as reader and using the password ETFbook1.
Preface | ix
ACKNOWLEDGMENTS
T
here are many people whom I’d like to thank and who, one way or
another, made this book possible. First and foremost, I’d like to
thank all those I’ve taught – whether in industry, undergraduate
students, or postgraduates, in the US or the UK – who have helped me
hone my teaching of this subject over the last 20 years. This book is my
answer to the many requests I’ve had for better, more-comprehensive
notes: I hope it suffices! Among the several thousand I’ve worked with, I’d
particularly like to thank the hundreds of teaching assistants I’ve trained,
and who have then helped me to help others. The hours we spent together
developing your skills have been some of the most rewarding and productive
of my working life (though not the easiest!), and the feedback and encour-
agement you’ve given me as you’ve seen the benefits in your own careers
has kept me going.
Another group of people to whom I owe a debt are those who have
written for me over the years and whose snippets of raw text I’ve used as
examples of good and bad practice. I’ve not named these contributors
because the text is old, unedited, and I didn’t want to embarrass them by
drawing attention to their habits (even if they were good!), but I think of
them every time I present these examples to students.
There are some specific people I’d like to thank. First, for more than a
decade, Rashik Parmar of IBM has reminded me – even when it felt like
no one else cared – that it is not just a luxury, but a priority for engineers
to communicate. Gary Lye, Chika Nweke (a former teaching assistant as
well as a valued colleague!) and all the staff in the UCL Department of
Biochemical Engineering also have my deepest gratitude for creating a
supportive work environment that allowed me to focus on getting this
book finished.
I’m also grateful to those who specifically helped me with Explaining
the Future. Colin Hayhurst (Innovations Partnership Fellow at the
University of Sussex) and Maurice Granger (chemical engineer and
Acknowle dgments | xi
former teaching fellow at UCL) both helped by reading and giving really
helpful feedback on drafts of the early chapters. Rose Gotto was extremely
encouraging and helped proof my book proposal for Oxford University
Press.
Which brings me on to Sonke Adlung who commissioned Explaining
the Future, Harriet Konishi, Elizabeth Farrell, and the rest of the team at
OUP. You made the editing of this book simple, straightforward and rela-
tively stress free (I wish the writing process had been as smooth). I would
recommend working with you to anyone. Thanks also to the production
team led by Lydia Shinoj.
I’d finally like to thank all my family for their help and support. One of
my brothers, Jon Bains, suggested that I develop canvases for the analytical
steps and helped me think them through. His time and thought were par-
ticularly invaluable. I also want to mention my nearest and dearest who
had the job of keeping me going during the day-to-day process of writing,
editing, and proofing the book while trying to get on with work and life.
You made this book possible.
1. Key Questions 1
2. Finding Answers 20
4. Analyze 51
7. Credibility 153
Epilogue 188
References 191
Index 193
Contents | xiii
CHAPTER 1
Key Questions
Explaining the Future: How to Research, Analyze, and Report on Emerging Technologies. Sunny Bains
© Sunny Bains 2019. Published in 2019 by Oxford University Press.
DOI: 10.1093/oso/9780198822820.001.0001
Key Question s | 1
to solve, and are trying to find the right technology to achieve that.
These two questions define two different perspectives, both of which are
important and both of which we’ll consider in the upcoming chapters.
We’ll start by considering the case of one specific technology and what
it can do.
Key Question s | 3
Question 2: What problem are you
trying to solve?
Often, with the claims we’ve discussed, there is an application implied: an
area where there is an existing problem that could be solved with the new
technology. For instance, if you take a performance claim, some company
might say they’ve developed the most fuel-efficient engine yet and imply
that it will make cars of the future more eco-friendly.
Validating this claim doesn’t involve redoing the efficiency measure-
ments. Although there are cases of scientific fraud that would make this
necessary, it’s not usually an issue. The problem is that this one measure of
performance does not tell you everything you need to know about whether
a development is likely to have a positive impact.
For instance, what if the high-efficiency performance only occurs for
steady highway driving, and the engine is actually less efficient than exist-
ing cars in the city? What if the engine requires new fuel additives, isn’t
compatible with current car design practices, or emits particularly toxic
pollutants? What if the engine design requires a lot of a very expensive
and/or scarce mineral?
These are not rhetorical questions: just because the engine has some
limitations or disadvantages doesn’t mean that it is useless. There may be
applications where it’s by far the best option. But, without understanding
the application requirements, there’s no way to answer these questions
meaningfully.
Another example to consider is as follows: a group is claiming that
they’ve created a computer using microelectromechanical logic gates.
This kind of logic gate is much less efficient than that used in standard
electronics: it is slower and heavier and takes up a lot more space on a
chip. Oh, and it’s much more expensive. Useless, right? Perhaps not, if
you’re trying to build some kind of failsafe device for a nuclear power sta-
tion. Conventional electronics can be very easily (falsely) switched when
exposed to radiation, and this makes them unreliable in any sort of disas-
ter. Mechanical switches, thanks to the fact that they’re less efficient
(require a lot more energy to switch) are more robust and therefore better
for this kind of backup system.
Bugs really can be features, and features really can be bugs. You only
know for sure if you get into the detail.
Technical requirements
We usually start with the technical requirements because, if these can’t be
met, the rest don’t matter very much. To get to grips with these, you need
to get to know the subject by exploring and interrogating various sources
and understanding their perspectives. We’ll get to these later. For now
we’ll focus on the questions to ask.
A technical requirement can be almost anything that—if the new tech-
nology doesn’t meet it—could prevent it from working, or working well
enough to be at all useful. One set of requirements would come from
thinking of the technology as a process with inputs and outputs: so, the
webcam algorithm we discussed earlier takes in image data and produces
an output that describes both where on the screen the user was looking
and what their emotional state was. The purification system takes in a
drug in a given form with a given proportion of impurities and then
pushes it out with those impurities reduced. Understanding what some
system needs to ingest and what it needs to spit out is critical to working
out whether it can do the job.
Another set of technical requirements relate to performance: how
quickly, efficiently, quietly, or accurately the process needs to be carried
out in order for a solution to be acceptable. The number of performance
measures that can be applied are as varied as the number of applications
served and the number of fields from which the technologies derive.
Many require deep subject knowledge to understand exactly why they are
important or even what they mean. Fortunately, that’s what experts are for
(we’ll discuss them at length in Chapter 2).
Physical constraints such as size, weight, and power (aka SWaP) can
be important in many applications. Whether or not a technology is viable
may depend on its size, its shape, its weight, its strength, or the number of
degrees of freedom in which it can move, and—although this may seem
Key Question s | 5
obvious—these everyday concepts mask a multitude of much more
technical ideas. Strength doesn’t mean anything per se: it’s tensile strength,
elasticity, hardness, and so on that matters. Which, precisely, are important
for a given application, and which are not, are what you have to determine
in your research.
Yet another issue to consider is what operating conditions a piece of
technology will have to endure, and its related working lifetime. If a cir-
cuit board needs to be kept below room temperature to operate, then
you’re unlikely to be able to install it inside a PC. If a building material
dissolves in acid rain, then—whatever other great properties it has—
you’re not going to want to use it in your roof tiles.
That these requirements exist may seem obvious and, when you’re in
the thick of trying to design a system, you’ll be acutely aware of what each
component or subsystem needs to do and/or withstand in order to fulfill
its role. Engineers won’t choose products or use processes that don’t meet
their exacting specifications when they are putting their own projects
together.
However, this doesn’t help us when we’re trying to evaluate technolo-
gies that don’t exist on the market yet. Essentially, we have to s econd-guess
what the requirements will be. Where one product is straightforwardly
just a replacement for another, it’s easy: the requirements already exist.
But some requirements are not defined explicitly. Doesn’t dissolve in the
rain is a key property of many building materials: so much so that we
might not have thought to write it down. However, the creators of an
advanced composite with many sophisticated properties might have over-
looked this issue if they were focused on indoor applications. As the one
evaluating whether the material could be useful for construction, it would
be up to you to make sure that waterproof was on your list.
Identifying the technical requirements for applications that don’t even
exist yet is even more difficult. It is possible to do this, however, as long as
you are willing to deal with some level of uncertainty. By making educated
guesses (or asking others to) about how the new application is likely to
work, drawing parallels with similar existing applications, and taking sub-
sets of their requirements that seem relevant and then thinking through
their potential points of failure, you can come up with a workable specifi-
cation. This won’t be definitive, but what it will do is give you some idea of
what is critical for success.
Key Question s | 7
A related concept here is exploitation. If an application requires a lot of
labor but is not expected to bring in much money, then the temptation
may be to pay the workers as little as they will accept to get the job done.
In some cases, this may be so little that either they cannot afford a reason-
able standard of living or they cannot afford to live without working an
unreasonable number of hours. Both of these are unethical, and, in some
countries, they are also illegal.
Environmental concerns are also important to consider. There are obvi-
ous issues, like the potential toxic sludge of our purification process, but
also many others that are more subtle. Life-cycle analysis is a tool that con-
siders the impact of a product (or potential product), from the mining and
shipping of the raw materials, to the energy used and pollution created
during production, to the disposal of the final artifact once it has broken or
become obsolete. For some industries, especially those related to nuclear
or fossil-fuel-based energy, environmental concerns—and the laws put in
place to address them—have had a huge impact on long-term viability.
There are fewer legal sanctions related to the impact on society of new
technologies. This is partly because they can be difficult to prove, partly
because society can be harmed without individuals feeling they’re being
harmed, and partly because some of the responsibility for harm has to be
taken by individuals themselves. Arguments are made about supermar-
kets causing us to waste food, video games causing us to waste time or
making us violent, and bad architecture preventing us from knowing our
neighbors. In the short term, such arguments may not matter very much
to investors. In the long term, doing the right thing often pays off.
Unethical behavior is not always punished, but both the law and political
scrutiny are having an increasing effect on how businesses run. In the UK,
for instance, corruption (aka bribery) has been illegal for some time.
Businesses not only have to behave ethically and conform to the law them-
selves but are expected to make sure all the companies in their supply chain
are doing the same. The most famous examples of such issues in recent years
have been related to the use of conflict minerals used in the electronics
industry (mined by people enslaved by Congolese militias) and the issues
surrounding the working conditions of Foxconn employees making iPhones
for Apple. In the former case, specific legislation was passed in the US requir-
ing the tracking of materials from their origin to make sure that conflict
minerals did not end up in consumer products. In the latter case, Apple was
forced to at least pay lip service to exhibiting better corporate responsibility.
Commercial requirements
If you thought that we missed some important issues in the technical sec-
tion, there’s a reason for that. Some important requirements look technical
but are, in fact, commercial.
Key Question s | 9
Compatibility is a good example of this. An application might be
technically possible without being compatible with anything (a lot of
prototypes are like this). However, selling a new technology often involves
it being able to work—at least in the short term—with equipment that
people already have. In fact, this factor alone could help a technology beat
its much-better-performing rival. What compatibility means depends on
the context: it could mean making sure your widget has the right connectors,
your process uses the right chemicals, or your data is in the right format.
It doesn’t really matter as long as you know in advance what’s required and
you understand that you may have to address your market segment by
segment if the compatibility issues are different for each one.
There is a whole constellation of requirements that are connected with
the issue of cost. If the technology is going to be used as part of a product
or service that is going to have to meet a certain price point when it sold
(whether that’s to consumers or business), this can affect everything from
manufacturability (how easy and cheap it is to make), to the materials
used, to overheads like server costs for cloud-based services connected to
products, to any labor involved, and so on. All of these issues are com-
pletely dependent on the application, and all of them have a direct impact
on the type of technology that can succeed.
And then there are the users and what they want and need. So many
would-be products start as a great idea in somebody’s head—and end up
in bankruptcy—because the great idea doesn’t appeal to or solve the prob-
lem of those who are expected to pay for it. Whole books are written on
the subject of business models and product design, both of which are far
beyond the scope of this one. But, at the very least, a reality check is war-
ranted. That involves going out and talking to people. We’ll talk about how
to do that in the Chapter 2.
Potential obstacles
With dozens of potential requirements, it may sound extremely time-
consuming to figure out whether a new technology will be derailed by one
of them or not. This might be fine for an investor or CTO, but not for a
researcher or student.
However, just a little research can take you a long way. Let’s say you’ve
been tasked to find out (quickly!) whether a new robotic technology—
developed for use in car manufacturing plants—could also be used as
robotic toys, as the company claims. Part of the work is done for you
Key Question s | 11
detail. Getting a really good feature set will allow you talk to a diverse col-
lection of people about potential applications: people from different
disciplines, those at different stages in their careers, and so on. If you have
a solution in search of a problem, you need to find the problem, and
brainstorming with others is the quickest way to do this. (There’s a canvas
to help you do this in Chapter 4.)
However, it’s important that you recognize that not all technologies do
have applications, and that not all applications are close to being marketable.
Limits
It may sound obvious, but growth cannot continue forever. Even Moore’s
law (the seemingly unending exponential increase in computer power) is
grinding to a halt, thanks to a combination of technical and commercial
limits. On the one hand, the challenges of manufacturing technology are
on the nano- rather than the micro-scale. Think about the relationship
between circuit density and yield. If you can reliably manufacture with, say,
with a few circuits per billion on a chip being faulty, then the number of
faults on a chip of a given size will go up with density. If you need a perfect
chip, that means you are having to throw away twice as many defective
chips for twice the density of circuits. You can get around this either by
improving your process to minimize the percentage of faults per circuit or
by introducing redundant circuitry (which duplicates the function of other
circuit elements) so that if something is broken, you can work around it.
That redundancy cuts the number of unique elements you can put in your
chip and, likely, the benefit of having a higher density in the first place.
The commercial pressures are just as real. Most people (most applica-
tions) don’t need more processing power, so if you build the equipment to
make the latest chips, you may not be selling to a very big market. Since the
Key Question s | 13
latest fabrication technology requires a lot of investment by manufacturers,
the chips they produce will be more expensive. This can quash demand.
In the case of chip manufacturing, the big issue that engineers had seen
coming for a long time was that of the end of the classical semiconductor.
Semiconductors work because one material is doped with another. For
every so many thousand or million atoms of one type, there will be one of
another, the dopant, that changes the semiconductor’s properties. While
this is fine when there are millions or billions of atoms in a circuit, the
system breaks down as the feature sizes get smaller. Because the doping can
only be controlled statistically (i.e. you know that roughly 1/1000 atoms is
going to be a dopant, but you don’t know exactly where that dopant will
end up) there could be circuit elements or areas where the dopant doesn’t
make it in at all, resulting in electrical properties that are not as expected.
As it happens, electronic engineers have found ways to work through
and get around this limit by being creative, and commercial and other
factors have ended up being far more important than physics. However,
I would argue that paying attention to technical limits, where they exist,
can help us to make better predictions about how technologies will evolve,
and such an approach has the advantage of being easier to predict than the
vagaries of supply and demand in an evolving marketplace.
Of course, every industry—indeed, every technology—is different.
There may be no equivalent of Moore’s law for the case you are looking at,
and no obvious point at which progress is likely to break down. This is
where you have to get creative, looking at the track records of technolo-
gies that have features similar to those of the new one. There’s no guaran-
tee that the analogy will hold up over time, but this kind of educated guess
will generally prove much more productive than none at all.
Getting started
Finally, it is important to remember that you cannot compare technolo-
gies that are in the market now with those that require development. Or,
rather, you can, but you must take account of this important difference.
Even if there seem to be few or no obstacles to a new technology entering
the market, getting there takes time. Businesses have to raise money, hire
staff, build infrastructure, and find suppliers. Just because a technology
Key Question s | 15
seems competitive today does not mean it will actually be competitive if it
launches four years from now. This has to be factored in.
It is not impossible to succeed with bad timing. However, with technol-
ogy being such a hit-and-miss business in the first place, good or bad
timing can be a critical issue.
Technology in development
Future competitors are more problematic to identify. These are not actually
in the market yet, but someone, somewhere, has high hopes for them. These
are harder to track down because, for instance, most journalists will only
judge a new technology on how it competes with what we use today. What
you want to know is how it will rate against a host of other technologies that
may already be in development for tomorrow. We’ll talk in Chapter 2 about
the kinds of techniques you can use to track down this kind of competition
(and their limits).
Key Question s | 17
Question 5: What are the features of
each competitor?
For every problem, there may be many possible solutions, each of which
has its own advantages and disadvantages. If the application is very nar-
row, some of these solutions could be ruled out very quickly because they
don’t meet the cost, performance, likely time to market, or other require-
ments. But that’s not always the case. Where it’s more finely balanced, the
only way to make sense of how the options compare is to do a kind of
audit, working through as many of the features of the solution as possible
that could work positively or negatively in any given situation.
This is an iterative process. A property that is advertised as a positive
feature for one solution may not be mentioned at all by those in favor of
another. Why? That’s what you need to find out. You also need to deter-
mine which of the features are most important to the different applica-
tions or market segments.
Determining both the various features of the competitors and how they
affect the applications are research-intensive questions (as are most of the
issues discussed in this chapter). Chapter 2 is about finding the answers.
Key Question s | 19
CHAPTER 2
Finding Answers
R
esearch is an iterative process. Whether you’re doing a PhD or
researching an investment, there is a process that involves loops,
diversions, and periods of refocusing. Although there’s no one
right way to do this, the following method may help you to get started.
The end of this chapter defines the various different sources of informa-
tion, explains why they are important, and provides some tips on how to
find the most relevant stuff. Even those of you who already have research
careers should hopefully learn a few tricks here.
First, however, let’s start with process.
Getting organized
From a practical point of view, you’re going to be collecting a lot of infor-
mation, and you want to be able to organize, reorganize, and search it
easily. An e-notebook can be ideal for this. For a technical analysis of the
type we’re looking at in this book, it makes sense to start by organizing the
notebook as follows:
• Primary technology: If there is one, this is the technology you’re thinking of
investing in, researching, sponsoring, and so on.
• Application(s): This is the list of potential application areas the primary technol-
ogy might address, or the one application that you’re interested in analyzing.
Explaining the Future: How to Research, Analyze, and Report on Emerging Technologies. Sunny Bains
© Sunny Bains 2019. Published in 2019 by Oxford University Press.
DOI: 10.1093/oso/9780198822820.001.0001
Finding An swers | 21
the features of the new technology are and so are happy to move straight
to thinking about applications.
This is only intended as a starting point to illustrate how the research
process can work: how you can set out to find answers to your questions.
If the particular starting point (focusing on “What can this do?” rather
than “What can do this?”) doesn’t work for you, Chapter 4 (on analysis)
explains how you can use different focuses (using canvases) to work
through different types of problems.
Finding An swers | 23
Researching today’s technology should be easy. It’s finding tomorrow’s
competition that’s hard, especially because, in any emerging industry, you
tend to find companies that are acting in stealth mode. They have every
intention of entering a particular market but don’t want anyone to know
about it. There can be many reasons for this: they may not want to give
their competitors any extra motivation to improve their offerings, they
may want to sign the contracts on funding from publicity-shy investors,
or they may be in the process of nailing down their intellectual property.
Despite this, there are a few techniques you can use that could allow you
to get a glimpse of the competition that is out there. First, if you want to
have inside information on an industry, tech bloggers can be really useful.
On the other end of the scale, in terms of formality, patent databases can
be a mine of information about who has been working in a particular area
recently. A variation on this theme, especially for consumer products, is to
search for trademarks, because the logos and product names that a com-
pany registers are a good clue to what they plan to bring out.
Famously, journalists are told that if they want to get to the bottom of a
story, they need to follow the money. In some cases, this can be true of
engineers too. If you’re trying to find long-term trends in a potential com-
petitor, annual reports—in conjunction with other stories in the tech-
nical press—can be helpful. If you’ve been following what a company says
about its direction in a few annual reports, then this—in combination
with stories in the technical press about the research it’s done, the people
it’s hired, and the intellectual property it’s licensed or registered—can give
you a very good indication about whether it is likely to become a competitor
in a particular area.
Going back to the technical side of things, another way to find competi-
tors is to identify the key publications of individuals involved. You then
use forward citations to find the work their papers have inspired, and
check to see who has licensed their patents.
A simple plan
If you were going to make your life as simple as possible while also being as
thorough as possible in your research, your project plan might look some-
thing like the following. First, you find a conference that covers the applica-
tion or technology you’re interested in. It doesn’t need to be the definitive
conference in the field, but it should do a reasonable job covering most of the
major approaches and giving you an introduction. Most importantly, it
should give you a good list of keywords for the next phase of research.
Next, you go away and do some research online, looking at the trade
press, technical literature, and patents. What are the major applications
and/or the most important features of any given solution? Which seem to
be the most important companies and research projects working on this?
As you identify key groups, you should try to make arrangements to do
site visits (if that’s possible within your time/money budget). Make sure
that each one informs the next and that, as new issues arise, you go back
and do the online research that will make sure that you understand them
fully. Be prepared not only with questions about the lab you are visiting
but also concepts that you do/don’t fully understand, issues relating to the
application, competition, and so on. This will ensure that you make the
best out of every opportunity and that, each time, you ratchet up your
own levels of knowledge, insight, and expertise.
Finally, you would go to another conference on the subject. This time,
you should find—even if you can’t follow all the technical issues—that you
have enough expertise to understand most of what you hear. You should
be able to see more clearly the similarities and differences between differ-
ent approaches and understand why they are (or are not) important.
Most importantly, this conference will give you the opportunity to talk
to other experts on an almost-equal level. In fact, if you’ve been able to
follow the rest of the plan, by this stage you should know almost as much
about what’s going on in the field (at least at a high level) as they do and
Finding An swers | 25
be able to ask really good questions. This will allow you to consolidate the
knowledge you have, as well as filling in any gaps.
We’ll deal with this last point in Chapter 3. It is key to understand that
everyone writes from their own perspective and agenda, and to figure out
what these are for your sources. If you can do this, it will make analysis of
the information you have gathered much more straightforward.
Types of sources
Keywords
These are critical to all research, because, without them, you will never
find the material you are looking for. Very different terms can be used to
mean very similar things: consider the relationships between artificial
intelligence and machine learning; hydrocarbons and oil and gas; and
CMOS and semiconductor processing. In each case, you might well find
information of interest if one keyword matches, even if the other (your
chosen topic) is nowhere to be found.
Keeping track of these keywords is worthwhile because they change over
time: words come in and out of fashion. Also, similar approaches to the
same problem may be called different things depending on your commu-
nity, your industry, and your institution. You don’t want to miss some cru-
cial information because you didn’t know the right keywords to look out for.
Search engines
The web is a brilliant source of information if you use search engines cre-
atively. The problem, of course, is not finding information at all, but finding
Technical
The technical literature
Journal articles, conference proceedings, and so on can be daunting
because each paper is written for a specific technical audience (which may
or may not include you). This means that most articles will likely be filled
with jargon. However, they are generally the most reliable account you
can find of a specific piece of work because they are (mostly) peer-
reviewed. This means their content was examined by other experts/
competitors before publication. They are great starting points for your
research, in part because the introductory section often highlights the sta-
tus quo and competing work, and in part because they include references
to related work that may be worth looking at.
Finding An swers | 27
These days, you can often find the papers you need using the web, but
accessing them may be a different story. If you are affiliated with a university
or a company that subscribes to a lot of journals, then it may simply be a
question of acquiring the right access credentials or going in through a
secure network. However, if you’re independent, it may be expensive to
get access. On the plus side, open access journals are becoming increas-
ingly common, and abstracts can almost always be found for free and may
be enough at the early stages of the research process.
One caveat, however: not everything is available using a typical web-
based search engine (even Google Scholar). There are often special collec-
tions of articles that are held by individual publishers, learned societies,
universities, and so on, and these would be difficult to find by doing a sim-
ple web search. If you have access to a technical library, it is definitely worth
tracking down any such collections that may have the material you need.
Another thing to remember is that there is often a long time lag (months
to a year) between when work is completed and when you can read about
it in the literature. This is another reason why talking to people can be so
productive. You can find out what’s going on now and ask for the latest
information. They might not give it to you, but even a hint can lead you to
another thread that you can try to piece together through other means.
One last thing: if you find that the technical literature trail goes cold
(you’ve been following a series of papers by a group, individual, or com-
pany, but they suddenly stop), it’s worth checking the patent databases
instead (see “Patents”). When a decision is made to commercialize a new
technology—or even to consider doing so—the emphasis switches from
publishing it to protecting it.
Finding An swers | 29
Commercial/technical
Patents
Intellectual property laws allow companies to protect their inventions in
return for releasing their ideas to the public. This trade-off is intended to
benefit progress in technology because, without the guarantee that no one
else can steal and profit from their innovations for a decent period of time,
everyone would keep them secret.
Until relatively recently, patent searches were expensive and difficult:
this is no longer true. You can now search patent databases like Google
Patents or Espacenet for free.
Patent databases are like any other: the better you are at searching, the
more relevant the information you will find. Remember to look not only
for solutions to a narrow technical problem but also for different ways of
addressing the wider application (at least initially). This will help expose
you to approaches you may have missed otherwise. Then, when you’re
trying to narrow the search, remember to focus on patents filed recently
(most likely for companies in stealth mode) and to think carefully about
the kinds of terms that you would expect to see in inventions related to the
problem you are researching.
Also, rather than target a subject, you may choose to target individ-
uals or companies who are doing work in a particular area. If they have
filed a patent, this may well be an indication that they intend to com-
mercialize it.
Once you have an interesting patent, you can use all the other tools
we’ve discussed to further research the company, licensees, the individual
patent holders, and even any new keywords. These links may lead you to
information about efforts in this area that could end up being important.
For instance, you might find more papers by the inventors, which give
more information about what the invention will most likely be used for, or
a story about how the company that owns the patent has done some kind
of licensing deal with a company in the application field. All of this is good
information.
Unfortunately, patents are deliberately written to be difficult to read. It’s
probably easier to consider them as confirmations of activity, or links
through to further information, rather than technical resources in their
own right. For this reason, you may find that your research involves sev-
eral cycles of talking to people, going to the trade press, going to the
2.
3.
You, that but hearing of my hated name,
Your ancient malice instantly bewray,
And for my sake your ill deserued blame
Vpon my legend publikely shall lay:
Would you forbeare to blast me with defame,
Might I so meane a priuiledge but pray,
He that three ages hath endur’d your wrong,
Heare him a little that hath heard you long.
4.
5.
6.
7.
8.
9.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
But their great force against me wholly bent
Preuail’d vpon my purposes so farre,
That I my ruine scarsely could preuent,
So momentarie worldly fauours are,
That till the vtmost of their spight was spent,
Had not my spirit maintain’d a manly warre,
Risen they had when laid I had been low,[2051]
Vpon whose ruine after I did grow.
55.
56.
57.
58.
59.
60.
62.
63.
64.
65.
66.
67.