We're generating a library of the projects, technologies, and
workflows that are paused, or “put on ice,” at Arcadia.
Overview
Learning is an important part of science. If we're doing it right, not
everything we attempt will work out like we expect. And in each of those
cases, there is a lesson that could be useful to others.
Why we ice
For more about Icebox and why we ice projects, read our
blog post
on the topic.
To make an impactful advancement, we'd need further technological or conceptual development.
We've decided not to pursue this area of science at the moment because it doesn't play to our unique strengths as a company.
We learned what we needed to learn from the project and there is no reason to continue.
What we discovered during the project lands us in an area where we lack internal expertise, or taking the project to the next step would require expertise we don't have (yet).
We tried to derisk a project, but could not overcome barriers that would enable us to move forward, or our hypothesis was wrong in a way that the remaining possibilities are not of interest for us to pursue.
The market is not appropriate, big enough, well-scoped enough, or is in an area where we are not well positioned as a company to have a competitive advantage. The time horizon to make this translationally actionable is too long or the challenges are too layered to align with translational goals.
The project can't be done without massive resources, it's inefficient, or we don't have a high-throughput approach to scan enough search space and have confidence we'll be successful.
We lack the facilities, equipment, or tangible resources to act on this project.
