Seeking feedback, embracing a growth mindset, and persisting through challenges — the habits that define a standout aspiring professional.
\n242\tProfessionalism and ethics grow through practice — asking for feedback, sitting with discomfort, and choosing to improve. Use the cards below to document your growth across these four areas.
\n270\tSeeking feedback, embracing a growth mindset, and persisting through challenges — the habits that define a standout aspiring professional.
\nProfessionalism and ethics grow through practice — asking for feedback, sitting with discomfort, and choosing to improve. Use the cards below to document your growth across these four areas.
\nA system for tracking business partner interactions, managing relationship history, and surfacing context when you need it — built on tools the program already uses.
\n200\tEach method fits a different situation. Most instructors will use two or three regularly.
\n244\t\n245\t#bprm-log. Claude identifies the partner, tags the sentiment, and flags any follow-ups — no form, no fields.These are available once you have a few interactions logged for a partner.
\n286\t\n287\tOne channel. No new app to learn or check.
\n328\t\n329\tThese run on every log entry without any extra action from the instructor.
\n378\t\n379\tFour things the BPRM addresses that no other tool in the current stack handles.
\n416\t\n417\tPartners return year after year. What student associates worked on, how it went, and what was discussed last spring — that context is available to whoever picks up the relationship next semester.
\n421\tWalking into a meeting knowing the last conversation and the state of the relationship changes how that meeting goes. The pre-meeting brief makes that preparation automatic.
\n425\tWhen a partner works across studios or an instructor transitions, the interaction history is shared and searchable — not trapped in an email thread or a mental note.
\n429\tEvery project tied to a partner, course, semester, and associates builds a record over time — useful for student associate portfolios, recommendations, and eventually the Alumni LookBook.
\n433\tWork through phases in order. Each phase depends on the one before it. Scenario A is the foundation — confirm it's working before moving on. Your progress is tracked in the nav bar above.
\n479\tA system for tracking business partner interactions, managing relationship history, and surfacing context when you need it — built on tools the program already uses.
\nEach method fits a different situation. Most instructors will use two or three regularly.
\n\n#bprm-log. Claude identifies the partner, tags the sentiment, and flags any follow-ups — no form, no fields.These are available once you have a few interactions logged for a partner.
\n\nOne channel. No new app to learn or check.
\n\nThese run on every log entry without any extra action from the instructor.
\n\nFour things the BPRM addresses that no other tool in the current stack handles.
\n\nPartners return year after year. What student associates worked on, how it went, and what was discussed last spring — that context is available to whoever picks up the relationship next semester.
\nWalking into a meeting knowing the last conversation and the state of the relationship changes how that meeting goes. The pre-meeting brief makes that preparation automatic.
\nWhen a partner works across studios or an instructor transitions, the interaction history is shared and searchable — not trapped in an email thread or a mental note.
\nEvery project tied to a partner, course, semester, and associates builds a record over time — useful for student associate portfolios, recommendations, and eventually the Alumni LookBook.
\nWork through phases in order. Each phase depends on the one before it. Scenario A is the foundation — confirm it's working before moving on. Your progress is tracked in the nav bar above.
\nStudents sign into the APEX portfolio with the Google account they already have, and save artifact evidence directly to Google Drive — using infrastructure Waukee already owns. No new passwords. No external services. One conversation with IT.
\nThis is the part that requires someone outside of APEX. Here's the plain-English version.
\n\n742819635047-abc123xyz.apps.googleusercontent.comOne button. The account they already use every day.
\n\nRight now, artifact cards have a link field — but students have to find, host, and paste links manually. With Drive integration, upload happens from inside the portfolio. The evidence and the reflection live together.
\nAny friction at login is friction that prevents students from getting to their work. Using the account they already open 30 times a day removes that friction entirely.
\nThis isn't a third-party auth service that charges per seat, has terms that change, or could go offline. It's Google's own infrastructure — the same system that authenticates every other Waukee app students use.
\nIT doesn't have to trust a black box. They approve a specific app ID, they control which student OUs it applies to, and they can revoke it at any time from the same Admin Console they use for everything else.
\nWork through phases in order. Phase 0 (Google Cloud setup) must be done before you can submit the IT request in Phase 1. Phases 2–4 can be built while waiting for IT approval — you'll just test with your own account until the student OU is approved. Your progress is tracked in the nav bar above.
\nStudents sign into the APEX portfolio with the Google account they already have, and save artifact evidence directly to Google Drive — using infrastructure Waukee already owns. No new passwords. No external services. One conversation with IT.
\nThis is the part that requires someone outside of APEX. Here's the plain-English version.
\n\n742819635047-abc123xyz.apps.googleusercontent.comOne button. The account they already use every day.
\n\nRight now, artifact cards have a link field — but students have to find, host, and paste links manually. With Drive integration, upload happens from inside the portfolio. The evidence and the reflection live together.
\nAny friction at login is friction that prevents students from getting to their work. Using the account they already open 30 times a day removes that friction entirely.
\nThis isn't a third-party auth service that charges per seat, has terms that change, or could go offline. It's Google's own infrastructure — the same system that authenticates every other Waukee app students use.
\nIT doesn't have to trust a black box. They approve a specific app ID, they control which student OUs it applies to, and they can revoke it at any time from the same Admin Console they use for everything else.
\nWork through phases in order. Phase 0 (Google Cloud setup) must be done before you can submit the IT request in Phase 1. Phases 2–4 can be built while waiting for IT approval — you'll just test with your own account until the student OU is approved. Your progress is tracked in the nav bar above.
\n