Skip to the content.
Home | Syllabus | Grading | Rubrics | Schedule | Resources

Syllabus

SCIE 4701 & 4702: Applied Innovation in Science

2026-27

Version 1.4, 2026-09-07

Instructor

Dr. Aaron Newman (Aaron.Newman@dal.ca)

Please call me “Aaron”; there is no need to call me “Dr.” or “Professor Newman”.

Office hours: by appointment. Please book a time using my Teams booking page. I would much rather talk with you early than find out at the end of term that something was wrong. You can also message me on Teams.

SURGE Manager

For matters relating to SURGE space, equipment, etc.

Sarah Roberts (SURGE@dal.ca)

Contents:


Dalhousie University operates in the unceded territories of the Mi’kmaw, Wolastoqey, and Peskotomuhkati Peoples. These sovereign nations hold inherent rights as the original peoples of these lands, and we each carry collective obligations under the Peace and Friendship Treaties. Section 35 of the Constitution Act, 1982, recognizes and affirms Aboriginal and Treaty rights in Canada.

We recognize that African Nova Scotians are a distinct people whose histories, legacies, and contributions have enriched the part of Mi’kma’ki known as Nova Scotia for over 400 years.


Course Description

Hands-on experience in using scientific training and knowledge to create innovative solutions to real world problems. Topics include stakeholder discovery, problem-solution fit, brainstorming, project management, pitching, and business models (including entrepreneurship and not-for-profits). Experiential learning format, including data acquisition and analysis, team work, case studies, and guest presentations.

Prerequisites

There are no specific prerequisite classes; however, undergraduates should have completed at least two full years (60 credit hours) of university study, if not more. SCIE 4701 and SCIE 4702 must be taken in the same year, and a grade will be given for SCIE 4701 only after SCIE 4702 is completed.

Exclusions

None.

Background and Rationale

This class departs from traditional science training by emphasizing the processes of innovation and commercialization: identifying problems that represent real needs in society and/or the world, and creating novel solutions that not only work, but are supported by a viable business model. Students will develop an understanding of how to design solutions that meet a real need, and have the potential to be commercialized or otherwise make it into the hands of people who can benefit from the solutions.

Students will find that the core principles taught in the class can be applied in a wide range of scientific and technological applications. This class will provide a unique perspective and new skills that are not typically offered in undergraduate or graduate programs in science or engineering.

Learning Objectives

At the end of this course, you should be able to do the following:

Innovation & Entrepreneurship

Personal/Leadership Skills

Course Format and Structure

This course uses an experiential, team-based format and relies heavily on a flipped classroom approach in which students assume responsibility for learning material (via readings and videos) and conducting activities outside of class time. Class time is then productively spent in discussing and interpreting content from the readings, presenting updates on project progress, and receiving feedback from other students and the instructor on these progress reports. The nature of the experiential learning process, and team-based activities, requires that students attend all classes and engage in all activities synchronously in real time during the scheduled class time. Please see the attendance policy below for details on missing class due to illness or other reasons.

Course Delivery

This course is delivered in person and synchronously. There is no online, hybrid, or asynchronous section, and class sessions are not recorded — the discussions and critique that make up most of class time depend on everyone being in the room together, and recording them would change how candidly people speak. Guest presentations are likewise not recorded.

Classes meet Tuesdays and Thursdays, 2:35–3:50 PM in SURGE — LSC O2660.

No course component requires attendance outside the scheduled class time, with one exception: Dal Demo Day on Monday 6 October, 1:30–3:00 PM, which is run by Dal Innovates rather than by this course. Attending is encouraged but not required, since the time overlaps our class start and you may have a conflict. Class that day runs 3:15–3:50 PM as a debrief, and is regular class whether or not you made the event.

Attendance and participation are essential requirements

In-person attendance and active participation are fundamental expectations of this course, not incidental to it. Virtually all of the learning, and effectively all of the assessment, happens in the room in real time: case and guest discussions, team activities, weekly update presentations, and the design sprint and final presentations. There are no lectures to catch up on, no recordings to watch later, and no papers or examinations that could stand in for being here. The graded work is your live contribution, discussion, and presentation. A student who is unable to attend and participate in class cannot meet the learning objectives of this course.

If you are unable to attend all or part of a class, please see Missed or Late Academic Requirements below for how to submit a Student Declaration of Absence.

If you hold an accommodation that exempts you from attendance, from in-class participation, or from oral presentation, please talk with me as early as you can — ideally before the add/drop deadline. Accommodations are determined collaboratively with the Student Accessibility Centre, and the large majority can be met here without difficulty; I would much rather plan with you than improvise in November.

There is one limit worth being honest about. An accommodation that adjusts how you meet a requirement is one thing; an accommodation that would require removing in-person attendance, live participation, or oral presentation altogether would alter requirements that are essential to this course and to its stated learning objectives. Where that is the case, it may not be possible to accommodate within this particular course, and you and I would work that through with the Student Accessibility Centre — that determination is theirs to make with us, not mine to make alone. This is not a reason to hesitate in coming forward. It is a reason to come forward early, while there are still options.

Course Outline

This pair of courses operates over two terms. Across both terms, students will build their understanding of the processes of innovation, commercialization, and entrepreneurship through team-based development of an innovative solution to a real problem, developing a business model for this innovation, and pitching their ideas to various audiences.

The class-by-class schedule is available as calendar entries on Brightspace. This includes required pre-class readings, videos, and assignments.

Fall Term (SCIE 4701)

The term starts with an overview of innovation and entrepreneurship, but the bulk of the term is focused on:

Winter Term (SCIE 4702)

The Winter term is devoted primarily to work on a single major project. These projects are conducted in teams, and involve engaging in customer discovery and design thinking to:

The culmination of these efforts will be a final lessons learned presentation in which each team describes the process they went through, the conclusions they arrived at (in particular, whether their solution is ultimately feasible), and what they learned along the way.

Class time during the Winter term will be 50% devoted to teams presenting weekly updates on the development of their projects. The other half of class time will involve presentations by guests from the innovation and entrepreneurship community, and additional case discussions.

Expectations

Workload

This is an intensive, honours-level course. Expectations are high. It may be the most demanding course you have ever taken, in its own ways. Unlike many lower-level courses, this course does not emphasize your ability to read, memorize, and regurgitate information. Instead, it focuses on higher-level skills that will prepare you for a variety of careers and future educational pathways — like combining information from multiple sources (including prior courses, life experience, and self-directed reading and research), analyzing information, and applying this information to solve problems. Importantly, these problems do not have pre-defined answers that the instructor expects you to reproduce; rather, you are graded on your ability to understand and explain a problem, and design and defend a viable model to solve that problem.

Students have reported upwards of 10 hours of work each per week on this course, outside of class time. In addition to the required readings (and viewings), getting out of the classroom and collecting data — in the form of interviews and independent research — is an important part of the class in both terms.

Radical Candour

This class employs a method of giving feedback known as radical candour. This is a method of providing direct, frank, and unapologetic feedback to students, particularly during the weekly business model updates. The two principles of radical candour are care personally and challenge directly. The goal of radical candour is to improve the quality of your solutions and business model — and ultimately, your critical thinking abilities — through honest and constructive feedback.

Most people find radical candour unsettling at first, because it dispenses with norms of politeness to the extent that these get in the way of making a point clearly. It is not intended to be aggressive or hurtful, or to criticize you as a person — but if critiques that feel abrupt, delivered weekly in front of your peers, embarrass you, be prepared to work through that discomfort. Teams perform better with candid feedback, and you can expect to be challenged and to have to defend your ideas throughout your career. It is by design part of emulating the pace, uncertainty, and pressure of a startup.

This is meant to work both ways. I expect you to question me, challenge my point of view if you disagree, and engage in real dialogue — clearly and directly, without making it personal. If you have concerns about the feedback you are getting, raise them with me; I will not penalize you for raising questions about your instruction.

Please note: this is not intended to present a barrier to anyone on the basis of personality or background. If you find the radical candour approach uncomfortable, but want to try it out anyway, then I will support you 100% and will be happy to talk with you privately or publicly about how to make it work for you. Many students in the past have started the course with a morbid fear of public speaking, and ended with confidence and A-range grades.

Receiving Feedback

An important part of radical candour is learning how to take feedback constructively. It’s very natural for humans to fall in love with their ideas, and to be defensive when they are criticized. You will be doing hard work and presenting ideas that make the most sense to you based on your research, and it can be uncomfortable — if not disheartening — to have them criticized. And, the feedback you receive may not always be consistent, or ultimately “right” — in innovation and entrepreneurship, there are many uncertainties and we are always operating on hypotheses and incomplete information.

When receiving feedback, be mindful of your natural human tendency to be defensive, and try to turn it off. Listen politely to the feedback, and thank the person for their input. It is rarely necessary or appropriate to argue with them, or explain why you made the decisions you did (unless you are asked directly). Indeed, in class there is very little time to receive feedback, and that time is best spent listening to the input of others, not repeating and defending your ideas. After receiving the feedback, you are still free to make your own decisions on how to proceed.

Team work

Much of the work in this class, and correspondingly the assessment components that determine your grade, is done in teams. The start of the Fall term will involve many short team activities in which team composition is determined by the instructor and varied each time. In this way, you will have the opportunity to work with all the other students in the class. Through these activities you should be able to make an informed decision when choosing teams for the Fall term design project, and the Winter term major project.

Team work has its challenges, but it is central to this class — to the learning outcomes, the activities, and the assessments — for one main reason: this course is about solving significant problems and implementing solutions through an organization, an entity larger than one person. Whether that is a startup, a social enterprise, a nonprofit, or a team inside a company or university, the work is beyond the time and talents of any individual. You will also, almost certainly, spend your working life on teams — often with a more diverse and difficult group than your classmates — where managing differences of opinion, working styles, and personalities is what lets a team do its best work.

Course Materials

Online Learning Platforms

All course information is provided through Brightspace.

Required Readings

These are not required but students may find them useful in the context of the class, and certainly if they pursue the topics of this class in the future.

Assessment and Evaluation

Evaluation of performance in this class is not based on how well you can memorize material. Rather, it is focused on how well you can apply the principles you learn in the lectures and workshops to real-world problems, and how you adapt your approach in response to feedback. As well, you will be assessed on how well you are able to communicate your ideas orally, including your ability to defend decisions you have made and explain the processes by which you came to make critical decisions in designing your business model. You will also be evaluated on how effectively you work as part of a team. Grading is a combination of formative assessments - relatively low-value items whose purpose is to provide you with feedback and guidance in your learning — and summative evaluation, which are relatively high-value items used to evaluate the outcomes of your learning and work.

There is no final exam in this course, and there are no tests or quizzes. No assessment component takes place during the December or April examination periods. Every graded component is listed in the tables below.

Grading

Grading will be according to the Dalhousie University standard grading scale. A grade will be given for SCIE 4701 only after SCIE 4702 is completed. The same grade will be assigned for both SCIE 4701 and 4702, reflecting the average for your Fall and Winter term grades. Your grades for each term will be available separately on Brightspace.

Conversion of numerical grades to final letter grades follows the undergraduate Dalhousie Grade Scale:

       
A+ (90–100) B+ (77–79) C+ (65–69) D (50–54)
A (85–89) B (73–76) C (60–64) F (0–49)
A- (80–84) B- (70–72) C- (55–59)  

SCIE 4701 (Fall Term)

Component % of final grade
Self-Reflections 5
Peer Assessments 5
Case/Guest Discussions 30
Weekly Project Update Presentations 10
Design Sprint Project 50

SCIE 4702 (Winter Term)

Component % of final grade
Self-Reflections 5
Peer Assessments 5
Case/Guest Discussions 30
Weekly Project Update Presentations 10
Business Model Presentation 50

Collaboration

Most work in this course is explicitly collaborative, and you are expected to work closely with your teammates on the design sprint, the Winter term project, and all in-class team activities. Talking through cases and readings with classmates before class is also encouraged — that is how the discussions get better.

Two components are individual and must be your own: your bi-weekly self-reflections, and your peer assessments of teammates. Do not complete these jointly or share them with the people they concern.

Please also see the Artificial Intelligence section.

Assessment Descriptions

Self-Reflections

You will submit regular (bi-weekly) reflections on your own learning progress over the term via Brightspace. Grading is pass/fail based on submitting something appropriate to the questions, or not. Late work will not be accepted. This is because the instructor will start reviewing them right after the due date/time (which is soon before Tuesday classes), allowing for feedback to be given in the next class.

Peer Assessments

Effective teamwork depends on effective teams. I can only have limited insight into the inner workings of a team, based on what I see in class. Effective teams will likely perform well in public, but the contributions of individual members to that effort may not always be balanced. Peer assessments are a mechanism to identify and reward the differences between strong leadership, effective contribution, and poor or unhelpful performance.

Peer assessment will involve bi-weekly surveys during each term’s major project (design sprint and business model project), as well as a final assessment at the end of each project. These bi-weekly formative peer assessments (meant to help improve performance) will serve as a check on the contributions of each team member. These allow me to keep tabs on any issues that might be arising. These are graded pass-fail: you will get full points for these as long as you submit them on time. There is a penalty of 10% per day for late peer assessments.

Summative (graded) peer assessments will be due at the end of the human-centred design project in Fall term, and at the end of the Winter term major project (i.e., at the end of term). In the summative assessment you rate each teammate on participation, preparation, communication, collaboration, and the quality of the work they brought, and estimate each member’s proportion of the project work.

Submitting the peer assessment itself is worth only a few points towards your final grade. However, it is also an opportunity for teams to identify individuals who did not contribute substantially to the project work. The peer assessment asks each team member to estimate the proportion of work done on the project by each team member. If any team member is identified by a majority of other team members as having done substantially less then their fair share of the work (“substantially less” being less than half as much work as others), the average contribution rating of all team members (other than the student in question) will be used to reduce the student’s grade on the team project.

For example, imagine a team of 4 members: A, B, C, and D. D slacks off and does little to none of the work, and members A, B, and C rate D’s contribution as 0, 2, and 4% of the project respectively (where equal work would have been 25% each). The team project receives a grade of 80/100 points. In this case, D’s grade on the project would be 2/25 or 8% of the points awarded for the project, i.e., 0.08 * 80 = 6.4 points.

Please note that this is a “worst case” scenario. We much prefer it if issues are identified before things get this bad. The bi-weekly formative peer assessments are intended to help catch these issues early. Teams should first try to contact the team member who seems to be doing less work, and discuss the issue with them to try to find a resolution. Secondly, before the project deadline, teams should contact the instructor to discuss the problem.

If you are on a team and are having trouble completing your fair share of the work, likewise please first discuss this with your team members, and if you can’t resolve it that way, please contact the instructor to discuss — ideally well before the project deadline. The purpose of this mechanism is to prevent students from “freeloading” on the work of others, but it is not meant to penalize people who are experiencing genuine struggles of any kind. The instructor is eager to support students who are struggling in any way.

Case Discussions

We will discuss a range of case studies focused on different topics relevant to the course. These serve both to teach material, and allow for analysis and synthesis of course content. Each student is expected to be able to make productive and substantive contributions to every discussion. Students are expected to raise their hands and be called on to speak. This allows more equitable sharing of air time. In particular, it is recognized that not everyone is equally comfortable speaking in class. Early in the course, the instructor will call on or otherwise encourage those who seem to need it. However, as time goes on and we build trust and psychological safety in the classroom, the expectation will be that you proactively raise your hand to contribute. Feel free to raise any concerns with the instructor about this. We will also discuss assigned readings that are not cases; the same expectations apply. Grading will be based on the Discussion Rubric.

Guest Discussions

Throughout both terms, we will periodically invite guests from the entrepreneurship community to class. These guests will normally make a short presentation, followed by time for discussion. As with case discussions, students are expected to actively contribute to these discussions in every class. Grading will be based on the same Discussion Rubric used for case and reading discussions. Note that contributions to guest discussions will only be graded if the instructor is present. If not, these will not contribute directly to your grade; however, the insights from these guests may provide valuable input that improves the quality of your other graded work.

Weekly Update Presentations

Both Fall and Winter terms involve a multi-week team project. In Fall term, it’s the Design Sprint (5 weeks), and in Winter term it’s the Business Model project (all term). Each week during these projects, students will engage in “customer discovery” interviews with potential customers/stakeholders, and iteratively develop a pitch for an innovative solution to a validated problem. Each team will be required to present a 10 minute update of their progress in class every week, followed by feedback from the instructor. These presentations are graded pass-fail, with a fail given only if no presentation is delivered, or if there is no evidence of progress (including integrating feedback) from the previous week’s presentation.

Design Sprint Project

The major project for Fall term is a multi-week design project. This is a structured process for developing and evaluating a novel solution to a problem over several weeks. This is completed in a team, and involves a number of in-class, facilitated activities, as well as work outside of class time. Outside of class, each team will be required to do work, including conducting research and interviews, and preparing the weekly update presentations. Each team will make a final presentation, which will be graded according to the Design Sprint Project Rubric.

Business Model Presentation

At the end of the Winter term, each team will describe their final business model and summarize the lessons they have learned along the way. This is not a pitch – it is recognized that not every effort will result in a viable business model. Rather, you will be graded on how deeply and thoroughly you pursued the development of the model, and how you reflect on all of the learning that has occurred throughout the course. This will occur publicly in a 15 minute team presentation. Grading will be according to the Business Model Presentation Rubric.

Missed or Late Academic Requirements

If you are unable to attend all or part of a class, please complete a Student Declaration of Absence (SDA) form and upload it to the Student Declaration of Absence assignment on Brightspace, which you will find under Assessments → Assignments. Please do not email it to me or send it on Teams — an SDA is personal information, and the Brightspace folder keeps it inside the University’s system. Note however that there is no benefit to you in submitting an SDA for a class in which no grading occurs. Most classes do include some graded component (e.g., participation, presentations), but use your judgement.

You may submit up to 2 SDAs per term. If circumstances mean you need to miss more than that, please contact me to discuss — ideally in advance. For reference, see Dalhousie’s missed or late academic requirements due to student absence policy.

Because nearly all assessment in this course happens in class, what a missed or late requirement means depends on the component:

Artificial Intelligence (AI)

Build with AI (optionally). Perform without it.

You are encouraged to use AI tools in this course — pressure-testing ideas, researching a market, drafting an interview guide, making slides, critiquing your own thinking before I do, building software and physical prototypes. In entrepreneurship, fluency with these tools is proving to be a real advantage over people who lack it, and pretending otherwise would be poor preparation for the world ahead of you.

But virtually every graded component of this course is something you do in the room — contributing to a case discussion, presenting an update, defending a design decision while I push back on it, answering a question you did not see coming. AI can help you prepare; it cannot show up. That split is the whole design: AI is welcome in everything that feeds your work, and the work itself is you, live, thinking on your feet.

The only asynchronous assessments are the self-assessments and peer assessments, which exist so that you can reflect on your own experience — empirically, this improves learning — and so that I can see how each of you is doing and catch issues common to several students. Each self-reflection includes a standing question on your AI use: what you used it for, what you changed about its output, and what you think you learned or skipped learning. It is pass/fail on submission, I am not scoring the answer, and “I didn’t use any AI this period” is a perfectly good response. I can’t prevent you from using AI to write these, but it would waste your opportunity and my time.

Why this matters more than any rule

Andrej Karpathy put it better than I can: “You can outsource your thinking, but you can’t outsource your understanding.” You need to understand what you are talking about well enough to explain your reasoning, walk through how you reached a decision, and do something useful with criticism. That is the specific set of skills this course exists to build.

Here is the harder version, now a central tenet in entrepreneurship: anything you can get out of AI, anyone else can get out of AI. It confers no edge, because it is not scarce. What is scarce — and what people are actually buying when they back you — is your ability to think, to reason under uncertainty, and to decide well on incomplete information. Those are skills: they develop through use and atrophy without it. Every time you hand a hard piece of thinking to a machine, you get the answer and skip the repetition that would have made you better at it.

Steve Blank, who has taught Stanford’s Lean LaunchPad — the model for SCIE 4702 — for sixteen years, watched his 2026 teams generate more product than they could validate, until “they started to believe that the product itself was the truth.” His conclusion is the one to carry into your project: the bottleneck has moved from resources to judgment — which problem to work on, how to read a weak customer signal, what to build next, when to abandon something you are attached to. AI supplies none of that, and is very good at reinforcing whatever beliefs you feed it. His full account is assigned reading in Class 5.

Your voice is the point

Do not bring an AI-generated script to read as your contribution to a case discussion. Reading aloud is not participation, and a real discussion requires you to respond to what the person before you just said.

For presentations, notes are fine — especially early in the term. But notes are talking points, not a script: point form, prompts for things you already understand. This has nothing to do with AI and applies equally to a script you wrote by hand; you cannot learn to present by reading. I may ask to see your notes afterwards if I have concerns — coaching, not enforcement. If you have an accommodation involving prepared text, come talk to me as early as you can and we will work out how to meet the objective.

There is also a practical reason to sound like yourself. People are reasonably good at spotting AI-generated content, and what your audience is judging is whether you are honest and whether you know what you are talking about. Careless AI use is among the fastest ways to destroy your credibility with an investor, professor, reviewer, customer, or hiring committee.

Three ways AI will cost you marks

These follow from the rubrics, which were revised for 2026 on the principle that what AI makes free stops earning points.

Using AI is not required

I encourage AI use. I do not require or expect it, and no assessment depends on it. The more you lean on these tools, the more you risk not developing your own capability. I also regard concerns about AI on ethical, environmental, religious, labour, or other personal grounds as entirely legitimate reasons to decline or minimize its use — the environmental footprint, the unresolved questions about training data and labour, and the documented biases in these systems are all real. Declining will not disadvantage you here. Two commitments follow:

Hard limits: other people’s information, and other people’s work

These are not pedagogy — they are law and licence.

Never put another person’s personal information into an AI tool without their knowledge and agreement. You will spend both terms interviewing real people, and the obvious move is to feed the recording to a transcription tool. Before you do:

  1. Tell your interviewee you intend to use AI to transcribe or summarize, and get their agreement. You are already asking permission to record — this is one more sentence, and standard practice in professional research.
  2. Strip identifying details first — names, employers, anything that pins the person down.
  3. Never, under any circumstances, for interviews touching health information, involving minors, or with anyone who asked you to keep what they said confidential. There is no consent workaround. Use your own notes.

The people who agree to talk to you are doing you a favour and taking a risk; carelessness here can cost SURGE a community relationship built over years, not just cost you marks. The same goes for copyrighted material you do not own — the course pack, other people’s papers and reports, material from the organizations you interview.

On tools. Dalhousie policy and NS privacy law let an instructor require only one generative AI tool: Microsoft 365 Copilot Chat, free with your Dal account and the option the University has vetted for data handling. I am requiring no tool, so use what you like — but anything sensitive belongs in Copilot signed in with Dal credentials, and that still does not absolve you of the rules above.

How I use AI — and how I don’t

I am asking you to be reflective about this, so I owe you the same.

If you have a concern about AI in this course that this section does not resolve, come talk to me.

Scent-Free Classroom

Dalhousie University has a scent-free policy which prohibits perfume and other scented products in the workplace. I have chemical sensitivities to certain perfumes, which can be unpleasant and disruptive, and other class members may as well. Please refrain from wearing scented products to class.

Accessibility and Accommodation

Dalhousie instructors and staff work collaboratively with students to create and sustain an accessible learning environment, as set out in the University’s Student Accommodation Policy.

Eligibility. You are eligible for accommodation on the basis of characteristics protected under human rights legislation, including disability and religion. If you have religious, cultural, or community-significant observances that conflict with course requirements — including the attendance expectations described above — please contact me and we will collaboratively find an alternative way for you to meet the requirement.

How to request an accommodation. To begin the process of requesting a formal academic accommodation, contact the Student Accessibility Centre. Accommodation letters come to me directly from the Centre, so you do not need to give me a copy.

Please talk with me early. As described under attendance and participation, in-person attendance, live participation, and oral presentation are essential requirements of this course. The large majority of accommodations can be met here without difficulty — and I would much rather plan with you in September than improvise in November.

Schedule

Classes meet Tuesdays and Thursdays, 2:35–3:50 PM in SURGE — LSC O2660.

The schedule below is subject to change. Brightspace is the official source for the schedule, and it will be updated whenever anything changes — dates, topics, guests, or pre-class work. Each class meeting is a Brightspace calendar entry carrying that day’s outline and any required preparation, so check there rather than relying on this table. Guest sessions in particular depend on visitors’ availability, and classes may be reordered as the term develops.

Fall Term — SCIE 4701

8 September to 3 December 2026. Study break 9–13 November.

Week Date Topic
1 Sep 8 Introduction to the Course
  Sep 10 What is Design Thinking?
2 Sep 15 Auto-Ethnographies
  Sep 17 Mini Design Sprint
3 Sep 22 Critiques and Future of Design Thinking
  Sep 24 Introduction to Neurotechnology
4 Sep 29 Leadership Simulation: Patient Zero
  Oct 1 Guest Speaker
5 Oct 6 Dal Demo Day + debrief — event 1:30–3:00 (optional); class 3:15–3:50
  Oct 8 Case Study: NeuroTrack and the Alzheimer’s Puzzle
6 Oct 13 Hands-On Introduction to Neurotechnology
  Oct 15 Neurotech Startup Founder Story
7 Oct 20 The Current Neurotech Industry Space
  Oct 22 Neurotech Design Sprint — Kick-off
8 Oct 27 Design Sprint: Customer Profiles
  Oct 29 Design Sprint: Brainstorming
9 Nov 3 Design Sprint: Value Maps and the Value Proposition Canvas
  Nov 5 Design Sprint: First-Pass Solutions
  Nov 9–13 Study break — no classes
10 Nov 17 Design Sprint: Revised Solutions/Prototypes
  Nov 19 Design Sprint: Work Session
11 Nov 24 Design Sprint: Final Practice presentations
  Nov 26 Case Study: The Founder’s Dilemma and Apple’s Core
12 Dec 1 Design Sprint Project Demo Day
  Dec 3 Crafting Your Life + Term 1 Debrief & Term 2 Planning

Winter Term — SCIE 4702

11 January to 13 April 2027. Study break 15–19 February.

Topics for the Winter term are not yet assigned to dates. The structure is described under Winter Term (SCIE 4702) above: roughly half of class time goes to teams presenting weekly updates on their business model project, and the other half to guest presentations from the innovation and entrepreneurship community and to case discussions. Specific topics, cases, and guests will be confirmed on Brightspace before the term begins.

Week Date Planned activity
1 Jan 12 Term 2 kick-off; project teams and problem selection
  Jan 14 Customer discovery: methods and planning
2 Jan 19 Weekly update presentations
  Jan 21 Case discussion / guest session
3 Jan 26 Weekly update presentations
  Jan 28 Case discussion / guest session
4 Feb 2 Weekly update presentations
  Feb 4 Case discussion / guest session
5 Feb 9 Weekly update presentations
  Feb 11 Case discussion / guest session
  Feb 15–19 Study break — no classes
6 Feb 23 Weekly update presentations
  Feb 25 Case discussion / guest session
7 Mar 2 Weekly update presentations
  Mar 4 Case discussion / guest session
8 Mar 9 Weekly update presentations
  Mar 11 Case discussion / guest session
9 Mar 16 Weekly update presentations
  Mar 18 Case discussion / guest session
10 Mar 23 Weekly update presentations
  Mar 25 Case discussion / guest session
11 Mar 30 Weekly update presentations
  Apr 1 Business model presentations — preparation and rehearsal
12 Apr 6 Business Model Presentations
  Apr 8 Business Model Presentations
13 Apr 13 Course debrief and wrap-up

There is no final examination in either term, and no assessment takes place during the December or April examination periods.


Syllabus Appendix: Student Supports & University Statements, Policies, and Guidelines

Dalhousie maintains a single, continuously updated page collecting the University’s policies and statements and the full range of student supports — academic integrity, accessibility and accommodation, the Code of Student Conduct, the Sexualized Violence Policy, fair dealing, grading practices, important academic dates, advising, the Writing Centre, Studying for Success, Student Health & Wellness, Student Advocacy, the Ombudsperson, the Indigenous Student Centre, the Black Student Advising Centre, the International Centre, and safety resources.

Please read it: Syllabus Appendix: Student Supports & University Statements, Policies, and Guidelines

It replaces the list of statements and links that appeared at the end of this syllabus in previous years, and it stays current as those policies change.