2023/10/11

#
>

10:06

→
#
>

Water of Ayole video for EM.411

→
#
>

Stopped at 5:10

→
#
>

What is the system being discussed?

→
#
>

To provide drinking water by transporting river water by using women holding buckets

→
#
>

Who are the stakeholders and what are their needs?

→
#
>

All water drinkers need safe water

→
#
>

The women who have to carry need a more stable way to transport water

→
#
>

Children who are most susceptible have a more dire need for safe water

→
#
>

What is the system supposed to do?

→
#
>

Sustain the village

→
#
>

While watching

→
#
>

Technology has not solved the problem

→
#
>

better to improve the analog system first before adding more components

→
#
>

At end

→
#
>

What is the system being discussed?

→
#
>

To sustainably provide drinking water by accessing underground water using a pump and a maintenance infrastructure

→
#
>

Who are the stakeholders and what are their needs?

→
#
>

All water drinkers need safe water

→
#
>

The women who have to carry need a more stable way to transport water

→
#
>

(new) The men who are responsible for maintaining the pump

→
#
>

Children who are most susceptible have a more dire need for safe water

→
#
>

(new) The institutions that install the pump need to reduce maintenance cost

→
#
>

the new ones essentially incorporate more of the social dynamics of the system (and pull in more of the surrounding systems)

→
#
>

What is the system supposed to do?

→
#
>

Sustain the village

→
#
>

Socio technical dynamics compared to my own experiences?

→
#
>

Internalizing maintenance cost into the system is often something that’s foregone in software since the cost to create can be so low

→
#
>

11:06

→
#
>

EM.411 meeting System Engineering

→
#
>

Is number of parts a good surrogate for complexity ?

→
#
>

What about size of team required?

→
#
>

Couldn’t parts be chunked groupings of more granular parts?

→
#
>

Iteration and recursion are inherent to System Engineering

→
#
>

progress from simple to detailed, approximate to precise, risky to acceptable

→
#
>

Feels like Agile development will follow naturally from this

→
#
>

The diagram looks like the workflows I built on jira

→
#
>

Maybe SDM should have a joint lecture from the professors to transition between the phases, might make for a very useful way to get aligned on how the different phases interface.

→
#
>

Product development process

→
#
>

Four “primary enterprise processes” for systems

→
#
>

Customer acquisition

→
#
>

Product development

→
#
>

Product realization (fulfillment, sales)

→
#
>

Customer support

→
#
>

Goals

→
#
>

Market fit

→
#
>

Business case

→
#
>

make money

→
#
>

Risk

→
#
>

balance

→
#
>

Resources

→
#
>

prioritize and allocate

→
#
>

Visibility

→
#
>

on status of development

→
#
>

Phases

→
#
>

Think about n+3 at the concept phase

→
#
>

Not today’s product, but the product three iterations out

→
#
>

Think about n+2 at the specify phase

→
#
>

Seems like Agile development sits in contrast to this

→
#
>

The difference between one-off vs iterative product development seems like it will determine how you want to hybridize between Product development process and Agile development

→
#
>

speaking specifically about more waterfall versions of Product development process I think

→
#
>

15:35

→
#
>

Storytelling and public speaking workshop at the Trust Center for MIT Entrepreneurship

→
#
>

Venture mentoring service

→
#
>

Storytelling is conveyance if the idea

→
#
>

Is it good to be a serial entrepreneur ?

→
#
>

Getting a couple big baloney vibes

→
#
>

ie hand wavy, soft non actionable,

→
#
>

I’ve definitely felt this way about other entrepreneurship stuff in the past

→
#
>

Part 1: Understand the audience

→
#
>

before you define the pitch

→
#
>

Part 2: Packaging content

→
#
>

You know too much, you need to simplify

→
#
>

Too much detail is a common pitfall

→
#
>

Separating the self from the content

→
#
>

Pitch

→
#
>

What is the clear path you are taking the audience down?

→
#
>

How does each point support your ultimate objective?

→
#
>

Elements

→
#
>

Problem

→
#
>

User

→
#
>

Market size

→
#
>

Technology/product/solution

→
#
>

Team

→
#
>

Progress to date

→
#
>

Next milestones

→
#
>

Match content to audience

→
#
>

Problem statement

→
#
>

Like a system definition in System Design

→
#
>

For MIX

→
#
>

To create joyful experiences by providing local art destinations using an augmented reality interface and platform

→
#
>

Part 3: Delivering your pitch

→
#
>

Less important than prior two

→
#
>

Elements

→
#
>

Physical presence

→
#
>

Vocal tone

→
#
>

Word selection

→
#
>

Performing under pressure

→
#
>

MIX thinking

→
#
>

The story is…

→
#
>

How we think about cities and public spaces are changing

→
#
>

Experiential entertainment is growing, resilient, and a true catalyst for joy

→
#
>

Leads to

→
#
>

An integrated Disneyland in every city

→
#
>

18:08

→
#
>

following up with reporter from ABC 11 about urban planning issues in Durham BPAC

→
#
>

Back in the US and following up from our call. I think these were the points I mentioned (listed roughly in order of time sensitivity):

→
#
>
  1. Fayetteville Street bike lanes project blocked. Project website: https://www.durhamnc.gov/3681/Fayetteville-Street-Bicycle-Improvements. BPAC letter: https://www.durhamnc.gov/DocumentCenter/View/52581/Sept-2023---Removal-of-Fayetteville-Street-in-CMAQ-Bike-Lane-Project-by-NCDOT. Should have folks from the community that we can connect you to if you’d like. My latest info on this as of a few days ago is that NCDOT has in some meeting acknowledged that they didn’t communicate well about this, but also claim the BPAC letter has some facts wrong (we have yet to hear what is incorrect).
→
#
>
  1. US 70 east study. Two designs have been offered, both of which increase car speeds through the corridor. Our basic premise is that there isn’t enough justification for building out this corridor for car throughput over local accessibility and safety, especially since the east end connector was completed and we know many developments are going up in this area. BPAC’s initial letter on this topic: https://www.durhamnc.gov/DocumentCenter/View/49553/January-2023---US-70-East-Concerns-and-Recommendations (we’ll be considering writing a follow up, possibly in tandem with Bike Durham).
→
#
>
  1. UDO update to follow the adoption of the new comprehensive plan. Processing kicking off in November and I will be taking part in one of the focus groups. Can fill you in more as that approaches.
→
#
>
  1. Multiple public comments over the last few months about sidewalk gaps. 2 specific types of issues: (1) sidewalks that are outside of city limits but within county limits, nobody is responsible for construction. (2) it’s too easy for a development to use payment-in-lieu to avoid building a sidewalk (we’ll be trying to change this with the UDO update). We have folks from the community who’d be happy to talk to you about each of these).
→